feat(content-types): allow custom root paths for CT managers #74
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.
Custom Path Support for Content Types Manager 🎯
Introduce a new feature that allows users to customize the path for the content-type managers' instance.
It aims to provide greater flexibility in how queries are made against Strapi app, especially those having heavy customization (or simply want to use the CT managers for plugins' models)
Custom Path Configuration
strapi.collection('foo', { path: '/plugin/baz/foo' });
strapi.single('bar', { path: '/my-custom-path' });
🧪 Testing
📚 Documentation
Documentation has been updated to include:
Related issue(s)/PR(s)
fix #24
Notes: