Fix incorrect import of unstable_useContentManagerContext in Helper-plugin migration reference#2367
Merged
pwizla merged 1 commit intostrapi:mainfrom Jan 22, 2025
Conversation
…ound in Helper-plugin migration reference
|
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
pwizla
approved these changes
Jan 22, 2025
Collaborator
pwizla
left a comment
There was a problem hiding this comment.
Thank you, @ahulterstrom!
The PR is now approved, merged, should be live on docs.strapi.io in a few minutes, and will be mentioned in the next weekly snapshot release.
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
3 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.
What does it do?
This PR updates an import path for the unstable_useContentManagerContext hook in the migration documentation for Strapi v4 to v5.
Why is it needed?
I don't know if importing from
'@strapi/strapi/admin/hooks'worked in v4, but it does not work in v5. The change helps developers use the correct import path as part of the migration process.