Update for api feature/6207#100
Merged
Merged
Conversation
…not implemented the function yet)
7riumph
requested review from
JustinTan-1,
graceeilori,
nataliey16,
xihai01 and
ysfabdullah
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does this PR solve or do?
Updates iOS apps intake for new
dualtoken payload created in api feature/6207 (api_token,refresh_token)What was edited, added, and or created?
src/components/context/AuthContext.tswithnewformat ofJSONdata's payload ( sign-in/sign-out, etc )package.jsonwith latestExpoVersionHow is this tested?
None yet. The payload is still actively changing.
Starting with a mock
HTTPtest for the/src/authBase/routeRequest.tswould be good as it'sfoundational.Screenshot/Video 📷
Note: Last
3lines within myterminalbelow show the newJSONupon apisign-into theQAserver with...Username as
volunteer1@example.comPassword as
12345678As per feature/6207 (
api_token,refresh_token) tokens arerandomizedon each sign-in attempt and thenewtoken expiry data is dynamically updated on token generation.Feelings gif (optional)
What gif best describes your feelings working on this issue?
