Lab 1 Blog

I reached out to students on Slack and found a student ready to peer evaluate my work. Stefan responded, and we both decided that working together would be beneficial. Python was a fascinating pick for him regarding a language to work in. It was unclear to me how to use his software. I am thankful that he assisted me with it. Incredibly, other people can detect issues in my code, mainly because there are certain bugs that I cannot see since they do not appear evident to me. I appreciate having people peer review. It makes me feel as if there is either something that might be improved upon or something that I was unaware of that was a bug. I discovered this when I was testing and assessing Stefan's application. I generated an input file in a directory on my own. The text contained inside a txt file would be read and then converted into an HTML file using this. I also discovered that encoding did not conform to the requirements for the function. 


Issues I filled: https://github.com/sfrunza13/SiteGenerationTool/issues/2 The code would crash when the input file was in a input path with a space in the directory name.

https://github.com/sfrunza13/SiteGenerationTool/issues/3 The code was not able to encode text properly.


Issues in my code that were filled: https://github.com/IvaniGabrovsky/text-ssg-tool/issues/1 Readme was empty. 

https://github.com/IvaniGabrovsky/text-ssg-tool/issues/2 The author of the program in the package.json is someone else's name. ssg.js does not seem to work as intended after npm install.

https://github.com/IvaniGabrovsky/text-ssg-tool/issues/3 outputFolder.isDirectory is not a function.

https://github.com/IvaniGabrovsky/text-ssg-tool/issues/4 Running the CLI tool with -v, --version -h --help options do not generate any output. But ssg.js does not seem to work as intended after npm install.


GitHub repos: https://github.com/IvaniGabrovsky/text-ssg-tool 

https://github.com/sfrunza13/SiteGenerationTool 


I was successful in resolving all of my concerns. It was a valuable experience since it taught me how to modify my code depending on other students' perspectives. I had the impression that it was a chance to be more open, avoid the sensation of being judged by other people, and make the most of the situation so that I might acquire knowledge that I lacked before. This experience taught me how to identify errors in the code written by others and provide solutions to the problems I found. In addition, when I finish my code, I shouldn't raise my hands and declare that I'm finished. There is always more that can be done to become better. There is always an opportunity for growth and development. A project is not considered completed as it can still receive updates regularly.

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