fix: use network-only fetchPolicy for tag table #254
Merged
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
Signed-off-by: Loan Laux <[email protected]>
3 tasks
|
Awesome @loan-laux Thanks! |
willopez
approved these changes
Apr 8, 2020
Merged
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.
Signed-off-by: Loan Laux [email protected]
Resolves #252
Impact: major
Type: bugfix
Issue
Newly created tags don't show up in the table on the Tags page because of the cache policy. Users need to refresh the page to see their new tags appear, which can be misleading and frustrating.
Solution
Use
fetchPolicy="network-only" for thegetTags` query.Breaking changes
None.
Testing