Issue #9 and #5 changes #11
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #5 tasks worked on:
Tasks:
I did not implement the pop up since I believe there are too many pop ups and there is relevant information inside the box for the user to figure out. If you believe a pop up is needed, I can add a pop up for it.
Still working on figuring out why old access tokens do not get invalidated. The check access to rerum api button
<input class='btn btn-primary btn-large' type="button" onclick="testAPI()" id="test_api" value="Check Access To RERUM API" />does not work as intended and shows that the previous access tokens are also validIssue #9 tasks worked on:
Login message is misleading – After logging in, the system shows “Registration successful”. This creates confusion because the user is not registering again; instead, it should display a clear login confirmation such as:
Checks button lacks useful output – On the main page, under Already Registered Information, the Checks button only shows a placeholder message instead of displaying relevant details(is this for first user or not, if i click on check what it will be there..)