feat!: remove cacheable property#43
Merged
thomaspoignant merged 2 commits intomainfrom Jun 2, 2025
Merged
Conversation
Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org>
thomaspoignant
requested review from
askpt,
beeme1mr,
jonathannorris and
lukas-reining
askpt
approved these changes
May 16, 2025
beeme1mr
approved these changes
May 16, 2025
Member
|
Just to be sure: the reason for removing is because for now we are not going to cache in the server? @thomaspoignant @beeme1mr |
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
4 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.
This PR
Remove
cacheableproperty because there is no plan to support cache in the providers before1.0.