Octoberfest Week 1 Blog

For this week, I worked in the Telescope project from Seneca. I added support for bulgarian language to the about page for Bulgarian speakers to being able to get a breaf understand of the Telescope project and how everything works.

I open a new issue for supporting bulgarian language on the overview page. I had to first fork the project. I cloned the project. I created a new branch using the command 

git checkout -b issue-3697 

Then in the directory src/web/docusaurus/ I ran the command 

mnpm i

to install the required dependancies into my project repo. Then I ran 

npm run start

and opened URL 'http://localhost:4631/docs/overview' to explore the about page and see how it looks. Then I created a new directory with subdirectories 

bg/docusaurus-plugin-content-docs 

with the overview.md. I translated the overview page content in Bulgarian. I also added the bg option in the docusaurus.config.js file located in 

src/web/docusaurus/docusaurus.config.js 

I was not sure how to run the docusaurus with bulgarian option. I asked on slack telescope channel. Someone from the project replied with the command. I ran the command 

npm run start -- --locale bg 

to run the about page with the bulgarian option.


I clicked on docs to see the overview in bulgarian. Then I added the changes in git. Then commited the changes on git. Then I pushed the changes. I created a new PR. 

https://github.com/Seneca-CDOT/telescope/issues/3697

https://github.com/Seneca-CDOT/telescope/pull/3700

Comments

Post a Comment

Popular posts from this blog

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/s...
Read more

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

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