-
Notifications
You must be signed in to change notification settings - Fork 432
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
feat(vision): link to edit documents #6124
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
Component Testing Report Updated Dec 4, 2024 11:30 PM (UTC) ✅ All Tests Passed -- expand for details
|
81f5cc7
to
ce0467f
Compare
ce0467f
to
dd5f187
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.
Love the feature! Been wanting this for a while :)
Is this "safe"? Ref #6074 the user might be querying another dataset 🤔 Though it provides an easy way to inspect a document.
For both features, perhaps we should grab all workspaces and try to narrow down the workspace in question based on the dataset. If we can find a single one, then use that workspace/schema. Else do not show the link, or show it as disabled with a tooltip ("no workspace configured for this dataset"). If there are multiple workspaces that references a dataset, we can temporarily show a "unable to resolve workspace for dataset", and then later expand it with a "select workspace to use"?
We'll need to expand our intent resolving, however - it currently does not allow specifying a workspace. It's something we've been wanting for other reasons though, so would make sense to add.
dd5f187
to
5604db9
Compare
Agree 😄 However, I had a look at injecting workspace into intent links, and from what I could tell it was a bigger refactor. So instead of that I pushed a change where we only render the document links if the workspace you are on matches the dataset vision is querying. Then the current behavior should work as is? |
5604db9
to
2f1cd7d
Compare
2f1cd7d
to
7142c04
Compare
⚡️ Editor Performance ReportUpdated Wed, 04 Dec 2024 23:32:26 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
* next: test(sanity): update timeout to avoid slow test from being flaky (#7969) v3.66.1 fix(deps): update dependency @sanity/presentation to v1.19.7 (#7966) fix(core): guard against missing process variable (#7967) fix(sanity): reset search cursor state when any parameter changes (#7889) fix(deps): allow react v19 as peer dependency (#7962) v3.66.0 fix: reword warning about vector images not support crop/hotspot (#7960) fix(deps): Update dev-non-major (#7959) fix(core): add telemetry debug/noop logger (#7958) fix(deps): update dependency @sanity/presentation to v1.19.5 (#7957) fix(core): only open one annotation object edit modal at a time (#7898) fix(cli): remove v2 commands (#5750) feat(cli): generate read token conditionally for remote template (#7953) fix(deps): update dependency @sanity/mutate to ^0.11.1 (#7903) fix(deps): update dependency @sanity/ui to ^2.9.1 (#7948) feat(vision): link to edit documents on `_id`, `_ref` attributes (#6124) fix(core): disable scheduledPublishing and tasks if `/features` returns error (#7517) test(e2e): restore last e2e tests (#7926)
Description
Suggestion: Add a link icon next to each _id and _ref attributes
What to review
Is this "safe"? Ref #6074 the user might be querying another dataset 🤔 Though it provides an easy way to inspect a document.
Testing
N/A
Notes for release
n/a - no notes needed