Mike Divine's Learning Journal

     This week, I have been fixing small requested changes and working to finish the Pull Request to have it accepted into the development branch, which will eventually become OED v2.0. I reworked the userDetails state inside the user components to be more concise and utilize checks for password matching and length. I also implemented a database migration that alters the user table to rename the email field to username as requested by our Project Manager.     I also worked on the CSV meter/readings upload components some more. I rolled back my changes to send back meter data from the server as my Project Manager decided he would rather just have the front-end re-fetch all the meters at this point in time. He feels this is best at this point because this significant change alters the documentation a lot and it broke some of the testing. He commented that we could look at this in a future PR and discuss it at a later time.     My plan for next week is to...

This week, I merged the development branches into our CSV and user-forked branches.  For the User branch, this was trivial and didn't take a long time.  However, the CSV branch had many conflicts that took a few hours to go through and make sure the correct code from both branches made it into the merged branch. The two branches both had some automated tests fail as they were designed for the previous versions of the code that myself and my team had altered. I worked to fix the CSV tests that failed to have them test properly against our new versions and pushed the code. Our Project Manager has now reviewed the code again and has some additional requested changes so I will work to get these completed and have it reviewed once more.  The main challenges are the Pull Requests I am working on are quite large and major pieces of the codebase, so they are scrutinized more and our Project Manager has specific requirements, so there is a lot of code to continually review, alter,...

This week, I made changes to the CSV pipeline and altered the API to return the meters that were created or altered and send them into Redux to update the global state. I also worked on the users' components to allow the user to update the email and added a note field which is also stored in the database.  In regards to the users' components, I also altered the create and edit components to use userDetails state to encapsulate all the data into one object state. My plan for next week is to merge the development branch back into the PRs as 120+ commits have happened since we initially forked from the upstream branch.  So there will mostly likely be some merge conflicts that I will need to deal with in order for our PR to be merged into the upstream development branch. Some of the challenges I have face recently are trying not to overstep when my team members are working on the same PRs. Some of them struggle so I want to help but then I don't want to do too much, while at ...

I worked on the User Components this week and updated the API to allow password changes. I also helped alter the User Components code layout to use the project formatting specifications. This makes the codebase easier to understand if you work on one set of components and then switch to another. I then worked on the CSV components to add validation to the input forms. My plan for next week is to make the requested changes by Steve and hopefully, he will accept the PR. Then I plan to continue to help on additional issues as needed or jump into a new issue if Steve has suggestions. The only ongoing challenge is continuing to learn as I go, keep a positive mindset and not let any frustration get me down. I will continue to research when needed and not be afraid to put in my best effort and fail, then try again.

This week, I worked to make a lot of requested fixes and changes by our Project Manager Steve after he reviewed the Pull Request. One of the big changes was the data upload user needed access to the meter names to make the current changes function as is and he preferred they not get that data.  They did have access to the meter identifiers so I had to change the data pipeline to use the meter identifier which was a very long process to track down everywhere the meter name was used and alter it to work with the identifier. My plan for next week is to complete any finishing changes that our Project Manager wants completed and then I have offered to help in their application security audit they are having done. I will also plan to get involved with any other issues I believe would be good for me to help with. Currently, the main challenges are troubleshooting issues and continuing to gather knowledge of the codebase. I am progressively gaining a better understanding of the codebase an...