Closed shgnplaatjies closed 2 years ago
I haven't committed new code to the code base since encountering this bug. Instead I've been debugging for a while and created this issue once I felt like this bug was beginning to take up a lot of time.
I've added a new branch (directly from this issue) and I will carry my stashed changes to this new branch attached to this issue.
I will pull request the clean, bug free feature to the code base (or work on another feature on the main and debug this later)
Solved issue.
Bug was in line 14, the print statement to log successful authentication. There was an invalid call to the api for api.get_user() which does not make sense in this context.
Description
Steps to reproduce.
Time of occurrence.
Expected Result
Actual Result
Dependencies, implementations and/or requirements whose development may be affected by this bug.
Link to original user story, acceptance test, or requirement (or copy pasted)
1 (this is the first issue tho. I didn't create a user story and acceptance tests for this one)
Assignees
Bonus!
Additional conditions that are required to reproduce.
User data of users who experienced the bug.