OGV-meteor VS OGV-meteor

Show appropriate errors when uploading a model fails. PR #105

Furthermore, I tried improving documentation. There was an issue opened in the project with the concern The current readme is arguable off-putting to new contributors. I added the CONTRIBUTING.md file to the project where I specified the commit guidelines, code of conduct, and PR opening process. I took the code of conduct guidelines from Covenant. The primary focus of adding the Contribution file was to thank and encourage other developers for contributing and keep a healthy environment to work with. I also added the table of content in the Readme file so the users can see what is in the Readme in a glimpse. I'll turn this PR to ready for review in a day or so as well.

The first enhancement I started in week 7 was adding custom background to the viewer where the user sees the model. This feature was requested a long time ago here. I used input type="color" for the color palette and fetched the color in the js file with the meteor events. This task was kind of related to three.js so I looked into the three.js docs about updating the canvas. I got stuck in one issue after updating the color it required the user to trigger zoom or interact with the model viewer in order to update the color of the viewer. After searched about updating the canvas after a change I found animate() and render() can update the canvas. Though I was a bit conscious about using render() because when the object is going to be larger it is gonna re-render the canvas. Anyways, this was the correct fix to update the canvas after updating color.

Then I fixed an old issue of splitting one main CSS file to multiple CSS files in this PR. By doing this, it became easier to handle and perform CSS tasks. In this task, there was a subtask of adding SCSS support to the project. Then, I added the node-sass meteor package to the project.

I started by adding Husky to the project. For that, I used this package. This was the most fascinating task. You must be wondering, eh!! that was easy for what thing I was most excited about. I didn't try installing husky before on any project. So, for me, it was nothing less than a roller coaster ride where I enjoyed a lot. Link to PR

The second week started on 14 June 2021 and ended on 21 June 2021. I solved the issue of Email server validation. This issue was if the admin has not updated the SMTP server details in application it should force the admin to setup first. This was required because if any user creates account the user was not getting any email, neither the user could recorver the password. Further, there was discussion for this task about setting up SMTP server at localhost. The full conversation can be read on the PR

The first thing I was doing when the coding period started was upgrading the Meteor version. This task was done already but I ran into a problem on my machine. I was not able to run any Meteor project on my machine. It took me a day to figure out the issue. I searched a lot about the issue and found some solutions from the internet and my mentor. I reinstalled the Meteor on my machine and removed .meteor/local folder and it got started again. The actual error was undefined symbol: node_module_register When I searched for the solution I found this error occurs when we compile the node modules with different versions from what we are using at the moment. You can have a look at the whole problem on stackoverflow. You can have a look on PR here

I'm glad to share that I've been selected for GSoC 2021 under the organization BRL-CAD for the project OGV. The moment I read the mail about my selection was endless. I was working for this event since I started my graduation in 2019.

Before we talk about week 3 here is the link of project board with cards that I'll be managing during GSoC 2021. I first thought to create a board in Trello but my mentor suggested creating under the project in my folk of project.