The work
For the upcoming weeks, I'm going to work on improving/fixing the sign-up area of the Telescope project in a series of issues.
I have done some PRs for the repo in the past and has become familiar with some parts of the related code. This helps me feel comfortable tackling issues regarding these part of the code. Since my previous PRs for the project often focus on display and arrangement of text and UI for improvement of user experience, I'm looking to get a bit deeper into how the code functions in the background in this big and complex project, to push the scope I work with.
The issues I have chosen are more closely related to the website handles user entries of their Twitch and Youtube channels during sign-up.
The issues
The first one is about the sign-up page incorrectly accept channel URL not chosen/confirm by the user.
The second one is about streamlining the overall sign-up process itself to minimize the need to repeatedly confirm ownership of the accounts/channels entered.
The third one is about incorrect channel URL(s) being shown after validating user entries.
Approach
First, I will need to look at how the code handles channel URL information in the background to see how I can fix issue 1 and 3. To tackle issue 2, I will need to trace the code to see how the code handles the sign-in form of each step to change how the sign-in process works.
After having understood the code, I would formulate some ideas of what to need to be changed and test the ideas, for each issue. If I have many solutions in mind, I tank them and go from the top choice first.
When I'm satisfied with the works, I would make PR(s) to get feedback from reviewer(s) and see if I'm missing something. Changes will be made according to discussions with them.
That's the generally format I would follow for each issue. Some issues might end up being more ahead than others.
Top comments (0)