Skip to main content

Setting a coding standard for Javascript world

 

Release 0.2.2 ~ 3...

Now I am in the middle of release 0.2 and it is very exciting and I am pretty sure I am enjoying it now. Today, I have learned how to set up the husky which is about when I try to commit codes, it automatically checks if there is an issue or unmatched rules to standard based on eslint and prettier.

Firstly, I added comment to get the responsibility of the eslint and prettier set up issue.

After I added the comment, I tried to get some advice to complete this issue and he made a comment about his favorite way of setting up husky. Here is the link which is very helpful since there are very specific format to set up and actually, it was almost the same except the main language. 

During the following the process, I realized another issue that he also created is very related my current issue so I also added a comment to take the issue and he gave a kind of agreement emoticon.

This was the eslint that I created after understanding of eslint. Prettier is simpler than eslint since it is only care of formatting. Not really difficult to contribute at this time, I think not only code but I realized that I can learn any helpful setting environment for developers like eslint, prettier and husky. 

After I committed my code , he finally took my PR and I saw that there were another automation tool which checked my code or PR. The name is vercel, which I have no idea now but I feel that I need to study.

In conclusion, I feel like that in the open source world, there are many people just wanting to help other people, having less skill, to improve their skills so I also should be open-minded to share my idea to broaden my horizontal of development world.




Comments

Popular posts from this blog

Getting more difficult?

  Release 0.2.4 Now I am at almost the end of release 0.2 and I chose the telescope as the final contribution. To be honest, this is huge, well organized and great project and it is first time to take a look. Unlike my previous assignment during the previous terms, there are tons of what I have never seen. First, docker compose is great and the document for contribution is very clear. Of course, I had no idea when read it first, but every time as my professor mentioned, there was a great guy, helper?, helping me a lot to set up the project. Although I had no idea about Elastic-search and Redis-cache server, I was happy to take a time to look though the codes and to understand. Again, trying to understand an issue is always hard for me and sometimes I am really not happy when somebody does not understand my question. This happened again. The reason why I attached the picture is that I am still confused about the whole process of this project especially about why frontend didn't get ...

Finally, release my first open source.

  Starting... This lab is to release my product to install easily. Instead of cloning or downloading and setting it up manually, it provides a lot of convenience for users to install it. I chose NPM since I used nodejs. NPM  is a great site to help develpers to release their git repository in the site.  Progressing... First, I signed up on npmjs.com and logged in the site on the console to release my repository. I had to set up a lot of things like 'npm init', modifying readme and package.json to be ready.  Second, I tried to release my repository by the command, 'npm publish --access public'. Unfortunately, the name, http-parser, was already taken, so I needed to change my name. I chose my name as http-checker and tried to release it again. At this time, I got 403, forbidden error. I spent a lot of time to figure out but it was actually due to not verified account. Once I got the verified email account, finally, I got the release version of my repository. Here is my...

Elastic search and more

  Release 0.3.1 Now it is time to learn what is Elastic search since the chosen issue is about adding more fields for our model in telescope.  This is very new for me so I was very scared when I started to work for this but now I think I am more confident. First, Elastic search is such a great supportive database especially for index search. The good thing is that it is not only the index search for whole value but, partial keyword as well. Of course, it may be wrong since I also just started to study it. Anyway, It was very careful when I read codes one line by one. Following the official document ,  I tried to add some fields, but it made some test failed so I needed to fix them. The below content is from the official document: Mapping edit Mapping is the process of defining how a document, and the fields it contains, are stored and indexed. For instance, use mappings to define: which string fields should be treated as full text fields. which fields contain numbers, dat...