feat(cms): remove cms-only filtering from getSchema, getSchemas #21
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
chore(cms)!: drop getSchemasFromOtherModules route BREAKING CHANGE: Removed CMS.getSchemasFromOtherModules (GET: /admin/cms/schemasFromOtherModules)
kon14
commented
Feb 8, 2022
kkopanidis
approved these changes
Feb 9, 2022
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.
CMS.getSchema and CMS.getSchemas now also return schemas not-owned by CMS.
CustomEndpoints remains blacklisted and therefore won't show up.
This PR also drops getSchemasFromOtherModules route as it's now pointless and unused in production, therefore branding as Breaking Change and deprecating straight away to avoid cluttering up the codebase.
@KostasFeg I believe Conduit-UI makes use of it to some extent?
BREAKING CHANGE:
Removed CMS.getSchemasFromOtherModules (GET: /admin/cms/schemasFromOtherModules)
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
masterbranchfix #xxx, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: