Skip to main content

Posts

Coding Standard

  Starting... This lab is to help our codes to standardize automatically. As you have experienced a lot, group coding is very difficult to be unified in one specific style. In this lab, we will explore how to make one style code with very efficient or effective libraries, prettier and lint for node js . Progressing... Prettier,  link , is great for matching our coding style especially indent with tab or space, how many line and so on. The first step I took is to install prettier and put simple scripts in package.json,   "prettier-fix": "prettier --write \"./**/*.{md,js,json}\"",  "prettier": "prettier --check \"./**/*.{md,js,json}\"". I just run the script and I realized that there were a lot of prettier issues like indent, different ending style, tab, space and so on. Luckily, these scripts were very helpful since it provided auto editing features as well so I did not have to modify following the rules manually.   Eslint,  li...

Working with telescope

   Starting... This lab is to help students to communicate with a big project, telescope, and understanding how to handle with the set it up. There were a lot of trouble since many of technologies are new for me such as docker, docker-compose, elastic search ladis, pino, and so on. Let's jump in the big project . Progressing... The first step I took is to install wsl 2. It is not very difficult since microsoft provides good instruction, link . Although the telescope provides very good instruction,   here , It was not really easy for me to get a concept and set it up successfully. Therefore, I needed to ask a lot of questions on slack, telescope channel. Some helped me a lot and explained so much and finally I got it work successfully.  After my server was working locally, I didn't have any issue to get the response from the url, http://localhost:3000/posts.  To communicate with the local server, actually I needed to change my code a lot since I wanted to sp...

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 ...

Don't worry about commit message

  Starting... This lab is to practice about the advanced skills on git such as rebase, squashing, and amend. What I had done before I learned this way to handle my incorrect committed message was like that, just doing reset and doing it again. I can say that I really love this skill especially about rebase and interactive amend mode. Progressing... Actually, This task is very simple and I understand the main purpose is not refactoring my code, but using the advanced git skills for my future journal in the code world. With the instruction of osd600, I made 3 commit messages to try to rebase for squashing three messages. pick   b77bdc5  applied three refactoring like used function, getting rid of global variables and removing duplicated regex and rename the methods squash   28059dd  got rid of global variables squash   66e551b  removed dupli...

How to communicate with other people

  Starting... This lab is to help students to communicate with the owner in open source world to solve the conflicts of merging their branch to remote origin. So, following the instruction, I forked one repository that I chose and create an issue to add new feature of ignoring url patterns from a file. git clone https://github.com/StellaJung-Student/project-checkurl.git Progressing... Actually, The main of my task is not about the implementation above. It is just helping another classmate to help his or her task complete. Of course I also have had the part from another student so I added his repository as another remote one. My issue on my repository is issue-11 so I typed following command. git checkout -b issue-11 pedro/issue-11 He did great for the task but I realized that he didn't modify readme for the feature of ignoring urls so I created issue-11-fix. git pull pedro issue-11 git checkout -b issue-11-fix pedro/issue-11 Git is actually so great since it automatically prov...

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. Pretti...

How to handle the conflicts of git

  Starting... This lab is to help students to solve the conflicts of merging their branch to master. So, following the instruction, I created two issues which are about  Create a filter for status code  and  Use color flag to use color output . Both of issues came from same commit position from master. Progressing... The first step I took is I added the new feature and commit and merge to master branch. From this OSD600 course, I have learned new library, Yargs, from the lecture video, and a lot of classmates already used it. Hm, I am a slow-starter LOL. Anyway, after applying the library and little bit of code change, I merged to master branch and there was no problems. By the way, following my professor's instruction, I tried to use  providing code to blogger, gist  to avoid using just image. And this is my first merge result. Next, I moved the issue-8, which is about color option from Node environment. To make the test easier, I used dotenv library. How...