content: use default sheets and named config files #262
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: Stephen Rugh <[email protected]>
sirugh
changed the title
herzog31
approved these changes
Dec 16, 2024
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.
Long ago we had, in starter content, a single config file with multiple named sheets within. These were prod, stage, and dev.
Since then, so that merchants can lock down their staging or dev configs, we have moved the configurations from sheets to files.
This ?sheet=prod is a remnant of before, and left to ensure backward compatibility. However going forward, merchants should either use the multiple sheets or the config service.
Merging this change may impact merchants who have the single config file, and who do not split their config files before applying this change.
Test URLs: