Detect Preview or Experiment Mode #144
Merged
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
…hether the current session is a preview or experiment session
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Added 2 methods and tests to determine whether the current session is a preview or an experiment.
The use-case for this is based around the idea that if you are caching rendered content separately to the cached api calls, you'll probably want to know if you're in the middle of a preview so that you can return fresh content to the editor. This is particularly relevant when you're working with content that doesn't directly relate to the document being previewed, for example cached layout elements/content.
Whilst the use case doesn't really hold for experiments, I don't think it hurts to have a helpful accessor that can tell you whether you're in experiment mode or not (?)