AAE-25816 Allow to set a custom storage prefix for Authentication #10225
Conversation
This file contains 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
alep85
requested review from
eromano,
popovicsandras and
DenysVuika
as code owners
alep85
changed the title
alep85
changed the title
DenysVuika
reviewed
Sep 17, 2024
alep85
force-pushed
the
fix/AAE-25816-fe-token-refresh-error-when-custom-ui-and-default-ui-are-opened
branch
from
c2e3541
to
e5528cf
Compare
DenysVuika
reviewed
Sep 17, 2024
| }); | ||
|
|
||
| it('should be created', () => { | ||
| expect(service).toBeTruthy(); |
There was a problem hiding this comment.
this test can be removed
…llow setting a custom storage prefix for authentication data stored in local storage
alep85
force-pushed
the
fix/AAE-25816-fe-token-refresh-error-when-custom-ui-and-default-ui-are-opened
branch
from
e5528cf
to
c3f5006
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
What is the new behaviour?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: