Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: ensure non-null resolver value in Editor #566

Merged
merged 4 commits into from
Oct 4, 2023

Conversation

ismajl-ramadani
Copy link
Collaborator

In my case, deserializeNode throws an error because the resolver object is being passed as null. This mostly happens if resolvers are constructed in an async way, and then passed to the Editor as a null object because of a bug in the client side, the Editor will not warn for the incorrect value of the resolvers and then later behave strangely.

@changeset-bot
Copy link

changeset-bot bot commented Oct 4, 2023

🦋 Changeset detected

Latest commit: 4c27535

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@craftjs/core Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link

vercel bot commented Oct 4, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
craftjs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 4, 2023 0:17am

@prevwong prevwong changed the title fix: checking for correct resolver value in editor fix: ensure non-null resolver value in Editor Oct 4, 2023
Copy link
Owner

@prevwong prevwong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! 💯

@prevwong prevwong merged commit f2b77fd into main Oct 4, 2023
3 checks passed
@prevwong prevwong deleted the fix-check-for-resolver-value branch October 4, 2023 12:22
@github-actions github-actions bot mentioned this pull request Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants