-
Notifications
You must be signed in to change notification settings - Fork 445
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
refactor: migrate @sanity/presentation@corel
codebase (#8312)
#8317
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
No changes to documentation |
⚡️ Editor Performance ReportUpdated Mon, 20 Jan 2025 10:04:41 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
Component Testing Report Updated Jan 20, 2025 10:04 AM (UTC) ❌ Failed Tests (5) -- expand for details
|
10b9d32
to
162a8cb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Cody! thank you for doing this, I have a few questions which are beneath!
Screen.Recording.2025-01-20.at.08.47.23.mov
Also, after testing out the presentation on the test studio I noticed that editing a version document seems to be broken (check the video), let me know if I can help in any way!!
@@ -483,7 +483,11 @@ export function turboChargeResultIfSourceMap<T = unknown>( | |||
} | |||
return changedValue | |||
}, | |||
perspective, | |||
// TODO: Update applySourceDocuments to support releases. | |||
Array.isArray(perspective) && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
huh interesting, why are we doing this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also jsut realised this code is the same changes as applied in the LoaderQueries.tsx should it be moved somewhere else so both can use it? Might be overengineering but since it looks to be the same code in somewhat seemingly related spaces
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the idea is for LiveQueries to replace LoaderQueries relatively soon. The rule of thumb we follow is that since only one of them will live on, we only make refactors that continue to make sense once LoaderQueries are deleted.
Does that make sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so, just wonder if we should write that explicitly on the component so the question doesn't come up later if we need to make more changes to both components 🤔
packages/sanity/src/presentation/overlays/PostMessageDocuments.tsx
Outdated
Show resolved
Hide resolved
162a8cb
to
110ebde
Compare
An update to this: looks like it's something that already happens in COREL, created a linear story for it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this! 🚀
110ebde
to
3eac310
Compare
Replays the changes in sanity-io/visual-editing#2081 on top of #8312.
Trying to make the diff here as small as possible so that we can iterate on presentation on
next
, and have less work syncing withcorel
❤