Feature/drafts load flag #679
Open
Conversation
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
This feature can be disabled by setting the env var: `LOAD_EXPIRED_ITEM_DRAFTS` to true. This will return the app to the legacy behavior of not using `expires` as a query constraint. > The feature flag is only temporary. Once this has run on production and there has been no issues, then remove the flag and default always to using the `expires` constraint. Once this is in place we can start to clean up the drafts collection.
…ft causes no problems
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.
when querying for item drafts use the expires constraint so that we only load drafts whose
expiresdate is in the future.This feature can be disabled by setting the env var:
LOAD_EXPIRED_ITEM_DRAFTSto true. This will return the app to the legacy behavior of not usingexpiresas a query constraint.