OSD release 0.2 intro post

For the release 0.2, I choose to work on the flow issue in debugger.html link. It is for maintaining the core health of the project. By adding "// @flow" to src/workers/parser/types.js, flow will check the JavaScript code for errors automatically. Check here for more information on Flow.

First, it introduces 28 errors:

I found there is a easy error to fix so I reduced it to 27. I am going to do my best and fix the rest of issues.

Comments

Post a Comment

Popular posts from this blog

Analyzing bugs for vscode on Github

Image
For the OSD600 lab3, I am trying to fix a bug for vscode. I found this bug in the issues tab,  Rename folder collapses it . The reporter illustrated clearly that when renaming the parent folder of a structure of folders, the folder tree collapsed. I analyzed the code and tried to fix it. I found that it actually deleting the folder structure first and then re-add them to the view with the new name. When rename the folder name: The folders get deleted one by one Then it will re-add it with new folder name  This is the code that has been doing the action. I don't know why it's done this way, but certainly there's reason for that. What I can do is to add code to expand the folders after they got added to the view.
Read more

Contributing for the open-souce projects to classmates

It is fun to help others' projects because I get the chance to learn different methodologies to implement the same logic. In the Release 0.1, I added supports for the Word document and Eslint to two classmates' Github projects. I improved my programming skills by reading many documentations when finding third party packages to fix the issues. It's a good way to learn.
Read more

OSD release 0.2 final post

Image
This was a valuable learning experience of working with the  issue  on Mozilla/devtools:  debugger.html . The issue was related to adding flow coverage for one of the type.js file. At beginning, I did not think it will be a hard process, just need to learned flow as I supposed to. However, it was actually not that easy because I ran into many troubles like figuring out the meaning of the code and make good adjustment for fixing. Thankfully, after I push my PR on GitHub,  here , Jason, the owner of debugger repo helped a lot. He fixed last three errors which really need deep understanding of the code. However, we all ran into the last problem, which is shown in the screenshots below, This error is tough because I am not sure what is it causing it. By doing some research, it might be flow itself causing the error. So, Jason asked me to created another PR just for debugging this error and merged other code to the master branch. Overall, my first contribution to open source projec
Read more