Use same cache level for MNTP no matter the output channel#15828
Merged
Zeegaan merged 1 commit intorelease/13.2from Mar 4, 2024
Merged
Use same cache level for MNTP no matter the output channel#15828Zeegaan merged 1 commit intorelease/13.2from
Zeegaan merged 1 commit intorelease/13.2from
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
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.
Prerequisites
If there's an existing issue for this PR then this fixes #15411
Description
The default MNTP cache level is
Elementsfor the Delivery API - but it isSnapshotfor Razor rendering. This seems to be the root cause for #15411 - so this PR changes the default cache level.Testing this PR
See #15411 for details.