Lab 3 Blog

I opened a new request issue to Add language support for Multi language. Issue#5 I also open a new request issue to add support for a horizontal rule in Markdown. Issue#6

Issue-5: When the user gives the option -l and the language and country. The language and country will be used in the string start part of html. I added a variable language for the language provided to my string start part of html. I added a condition to check if language is provided by the -l parameter if it is not provided I am using default language en-CA. If it is then I will add it as the language to be used. I added to the console log the language to be display to the user in the success message. I added a parameter in the processFile function to be used as the language in the object generateHtml. I also added a parameter in the processDir function to be used as the language when calling the function processFile if the full path is a file. I also added language in the generateHtml function when calling getStartHtml function.

Issue-6: In case processing files is markdown I added the logic calling the function processMD passing the data as the markdown text, and "---" for the pattern, and "<hr>" for the opening tag, I left the closing tag with an empty string as the bar tag is used every time "---" is found.


Issue-5: I created a new branch using the command 

git checkout -b issue-5

 I switched to the branch using the command 

git checkout issue-5

I added the changes in runSsg.js. I commited the changes using the command 

git commit -m "" 

I used the command 

git checkout main 

to switch to the main branch. I then used the command 

git merge issue-5

 I did not get any merge conflicts.


Issue-6: I created a new branch using the command 

git checkout -b issue-6

I switched to the branch using the command 

git checkout issue-6

I added the changes in runSsg.js and inputMD.md. I commited the changes. I used the command 

git checkout main 

to switch to the main branch. I then used 

git merge issue-6 

I did not get any merge conflicts.

I used the command 

git push origin main 

to push the changes to github.

I closed the issues on github.

https://github.com/IvaniGabrovsky/text-ssg-tool/issues/5

https://github.com/IvaniGabrovsky/text-ssg-tool/issues/6

Comments

Post a Comment

Popular posts from this blog

Lab 8 Blog

In this project, I used jest as a unit testing framework, which Facebook created. It makes it easier to test UIs and javascript functions. It has features like a built-in assertion library, code coverage, and mocking. It is now a full set of tools that can be used for my JavaScript project. By running multiple test suites at the same time, Jest can speed up the testing process as a whole. I choose Jest as my testing framework because using mocking in test cases was important to me when testing functions, as it helped me to test values that are not real. To set up my project. First I ran the command  npm install to install all module dependancies.  Then I ran the command  npm install --save-dev jest to install the jest module as dev dependancies. Then I added the script "scripts": {  "test": "jest"  } I learned while writing my test cases that making test cases for each function was unnecessary. Some of my functions were calling other functions. Also, I rea
Read more

Octoberfest Week 2 Blog

Image
For this week, I worked in the open source md-page  project.  I fixed a bug where npm run test fails: 18 snapshots failed.  issue 60 I open a new issue npm run test fails: 18 snapshots failed. I had to first fork the project. I cloned the fork. I created a new branch using the command  git checkout -b issue-60   Then I ran the command   npm i to install the required dependancies into my project repo. Then  I ran  npm run test to test the project. I found that the command was giving me errors because test snapshots were not updated. I then ran the command  npm run test -- -u to update the test snapshots. Then I ran npm run test to test the project.   Then I added the changes in git. Then commited the changes on git. Then I pushed the changes. I created a new PR.  issue:  https://github.com/oscarmorrison/md-page/issues/60 PR:  https://github.com/oscarmorrison/md-page/pull/61
Read more

Lab 9 Blog

In this project, I created my GitHub Actions Workflow by going under the actions tab and selecting Webpack for my workflow. Then I committed the webpack.yml file with the default value without changing anything. Then my workflow got executed, and everything was successful. I got the green checkmark for all builds. Then I created a bug. Then I added the changes in git. Then commit the changes on git. Then I pushed the changes. Then my workflow got executed, and the workflow failed on the build. Then I fixed the bug. Then I added the changes in git. Then commit the changes on git. Then I pushed the changes. Then my workflow got executed, and everything was successful.  My partner's testing setup had lint running right after any commit. Writing test cases for a project I did not create required time to understand how the code was working and why my test case was failing before making the modifications in the code to have the test case I created to be successful. PR: https://github.com
Read more