HaoyuBlog

This week I was working on my second bug on the thimble repo. This one is a feature request. Here is the link to the issue https://github.com/mozilla/thimble.mozilla.org/issues/2506. I basically need to add a inline editor for editing the Border-radius css rule. Something like this: I already made it partially working. But some of the UI style still need to be fixed. As you can see right now the background color is all read which does not really meet the production level standard. At the first glance of the issue. I didn't think this should be taking too long, because there are already some existing inline editors code example. I thought I can just do bunch of copy-paste to make it work. However, when I really sit down and starting working on it, it was totally different than what I thought. You need to have different files to handle different behaviours of the editor. To figure that out I started by reading the existing code over and over again. That took me a long time to g

This week I was trying to add the travis CI component to my test repo. The setting up doesn't take too long to figure out. In my case, since I'm only using node JS, all I need was just to specify the node js version in my travis.yml file. In my opinion, CI tools are very useful when you trying to manage a open-source project with thousands of contributors. For example, you can use travis to automate the build process before you merge others code into your master branch. If the code was incompatible with the existing system then the travis will detect the error and merge can be blocked. On the other hand, you can use travis to make sure all dependencies are being installed by stating the scripts in the .yml file. Basically, I think travis works as if a real person who does things based on the instructions you give. Image when thousands of people working on the same project, they may all have different coding styles. Without CI, your repo may become messed up. Below is th