Open Source - Wei Huang

     In my previous blogs, I have planned out my release 0.4 contributions, I have been reading documents and watching tutorials, communicating with the developers of the project ever since. Today, I have finished my two contributions on the qasong repository. In the previous blog, I have talked about how I fixed one of the issues, in this one, I will talk about the other.     The second issue, which I considered to be the more challenging one, is an issue I opened in the repository myself, this is an issue I created from one of my release 0.2 contributions. The confirmation button on the clear queue section, produces a browser default confirmation window, I really should have worked with Material-UI based component to make a dialog component myself since this is the framework that the project relies on. The browser confirmation window looks ugly, but it got the job done, since I didn't know how to work with most Material-UI components back when I was worki...

     In this blog, I will provide updates on my previous post , in the previous blog, I have set my plans and goals for 2 of my release 0.4 open source project contributions. Since then I have been working on those issues and have done a good amount of work.     I started with the issue which I thought would be easier to solve, that is to add a Material-UI based component to alert the user that the song queue has been saved once they click the save queue button. This issue itself didn't seem too challenging in the beginning, but in the middle of implementing this, I was able to find many parts of the code that is some-what related to this feature that needs improvements or some debugging, therefore, aside from implementing the save alert, I also fixed those issues. The list of issues that I fixed could be found in my PR .     After I requested for the issue mentioned above, one of the the qasong team member sent me a document on Material-UI Alert comp...

Working with open source projects could be difficult, sometimes planning ahead of time could be helpful. During the past few days, I have been trying to find issues to work on, something that is challenging but could also be implemented within a couple of days, after a while of deciding what project and issues to work on, it occurred to me that there is something that I can do. While working on release 0.2 project few weeks ago, I ran into an issue in a music queuing web application GitHub repository named qasong , that is to add a clear queue button and prompts the user for confirmation. Therefore, I went ahead and added that new feature to the project. The new functionality behaves normally and works, the PR for this issue was eventually reviewed and merged, but I was not satisfied with it. While working on this issue, I was stuck on the "confirmation" part, the application was built with Material-UI components, but since I didn't have much experience with Material-UI,...

Back then when DLCheck had very limited functionalities and features, I decided to release the project and hosted it on npm, that was probably not a good idea because the project was incomplete and needed more features and test. Today, I have pushed 4 versions in total and I am happy with how much I have added to the tool. Steps I took to push to release to NPM:     - Go to package.json.     - Give project a name, a main entry point and bin (mine is index.js).     - Give project a version number, this will be the version number showing on npm after you push it.     - Register an account on npmjs.com .     - In the command line, run "npm publish" command, it will ask you to log in using the account you just         registered. I asked a friend of mine who is also a programming student to follow my README in order to install the DLCheck npm package on his end and test the tool, the process was smooth since he has e...