Add basic strapi5 compatibility option #36
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
DeppsOpz
changed the title
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.
This PR adds a strapi5 compatibility option to address some breaking changes made in the API.
This has been tested with a fairly basic strapi5 setup, so not all breaking changes in v5 may be covered.
v5compatas site optionStrapi-Response-Format: v4to requests if v5compat is true (https://docs.strapi.io/dev-docs/migration/v4-to-v5/breaking-changes/new-response-format)document.documentIdinstead ofdocument.idwhen making requests if v5compat is true (https://docs.strapi.io/dev-docs/migration/v4-to-v5/breaking-changes/use-document-id)