OSD600- Release 0.4 Part 2

 To prepare for the issue I am planning on doing for release 0.4 I spent this week reading the code and learning how to view and test the login component I will port from gatsby to next! I first added the folders needed to the next/ directory and copied the LogIn component to next/components, this way everything will be organized while I do my work. One road bump was figuring out where and how to call the components for testing, but after careful study of the code, I learned how to do it. I then comment out the code in index.tsx and called the login component. It didn't work! I realized that since I have not ported the component to next I will not be able to call it from the index.tsx. I have begun reading how to port components and already made some small modifications (eg. changing the hrefs). This week was dedicated to planning and understanding how everything works. I used to think that's not so important, but based on my past experiences I know this will pay off next week! Now I feel more ready then ever to port this component. There are still some things I am unsure of (how to port functions) I am planning on spending the weekend figuring this out. If I still run into issues I will ask for help on Slack. I spent much of this week on lab 9. I like to finish one thing at a time, my plan is to clear my schedule (which I already have) and put all my focus on this. I know this was a pretty slow week in terms of progress on release 0.4 but it will be worth it! 



Comments

Post a Comment

Popular posts from this blog

OSD600 Intro Post

Introduction: Hello, my name is Joey and I am a student at Seneca studying Computer Programming. My whole life I have always been interested in technology. Towards the end of high school, I enrolled in Computer Science and enjoyed the subject. My passion for technology and love of code persuaded me to get an education in Computer Programming. Why Are You Taking this Class? I am taking this class to help widen my skill set and also because I have always been interested in Open Source. I know many programming technologies such as Java, C++ and SQL but I don't know anything about Open Source. It has been a goal of mine to learn but never had the time to look into it. Therefore, I decided to take this class as I believe this is one of the best opportunities to learn!  What is it About Open Source that Attracted You? The freedom the comes with it. I am fascinated by the idea that anyone can take my code and work with it, and I can do the same to theirs. I believe the more people that co...
Read more

Git Workflow When Contributing to Open Source

The following are the steps/workflow you follow when you find a repository on GitHub and wish to contribute to it.      When you find an issue you wish to work on in a  repository , first fork it to your GitHub, then clone it and make a new branch (you will be working off this new branch. Its a good idea to name the branch after the issue you are planning to fix Eg. issue-2) . When you are done with your code push it to the new branch you made for the issue/feature then create a pull request ( pull request is a review request You are asking someone to check the changes on a branch before merging into another branch. ) The person who owns the code will check your code and if it's approved it will get merged with the original. 
Read more

OSD 600 Lab 2

I really enjoyed this lab as is helped me understand the process/workflow of contributing to open source. I wrote a separate article on that which can be found here .  During this lab, I created an issue  on the original repository saying I wish to implement additional features to the code.  Once I got approval from the original author to do this I forked and cloned the project, created a new branch called issue-2 , and uploaded the code I wrote to it. After that, I made a pull request to the original repository. For my feature, I added the v and version arguments to their command-line tool. The process of getting my work accepted was exciting as I got to hear from the person who wrote the code and learn what it is exactly they want. This a great opportunity to improve on the code you wrote. One problem I had was after I got the feedback I was not sure how to edit code on the issue-2 branch, after doing some research I learned how to switch branches via the git checkout...
Read more