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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(parameters): AppConfigProvider to return the last valid value when the API returns empty value on subsequent calls #1365
feat(parameters): AppConfigProvider to return the last valid value when the API returns empty value on subsequent calls #1365
Changes from 3 commits
0b90940
2d80baa
3fea0d7
838c341
f16d3a5
3aeacb8
d246306
3bde508
6e15a09
ba6e8db
61f6476
3c46d0c
cead3f5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to reword this to reflect that we are no longer using the delay but instead avoiding cache with
maxAge: 0
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the only test using this reset. We should possibly add a
afterEach()
block to the whole test fixture that does it so that it gets applied after every test.Maybe we can do this for this file, and then possibly in a future PR we can also apply the change to all other tests under
packages/parameters/tests/unit/*
.What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, that works for me. I added it here to be surgical - the
resolvesOnce
chain was acting weirdly without it. I like the consistency of using anafterEach
instead.