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(core): set default placements for certain studio popovers #4963

Merged
merged 1 commit into from
Oct 2, 2023
Merged

Conversation

bjoerge
Copy link
Member

@bjoerge bjoerge commented Oct 2, 2023

Description

The new default fallback placements for popovers released in Sanity UI v1.8.2 are good for most use cases, but in the Studio it has been causing issues for popovers used by the reference input, cross dataset reference input and the document type selector used by the array input.

This PR fixes these issues by explicitly choosing better fallback placements.

Before

image

What to review

Make popovers used by the following components places themselves where they should and renders nicely:

  • reference input,
  • cross dataset reference input
  • the document type selector used by the array input.

Notes for release

  • Fixed rendering issues with certain popovers being caused by wrong placement

@vercel
Copy link

vercel bot commented Oct 2, 2023

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

Name Status Preview Comments Updated (UTC)
performance-studio ✅ Ready (Inspect) Visit Preview Oct 2, 2023 0:43am
test-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 2, 2023 0:43am
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
studio-workshop ⬜️ Ignored (Inspect) Visit Preview Oct 2, 2023 0:43am

The new default fallback  placements for popovers released in Sanity UI v1.8.2 are good for most use cases, but in the studio it has been causing issues for the reference input, cross dataset referenc and document types button popover.

This PR fixes these issues by explicitly choosing better fallback placements.
@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2023

No changes to documentation

@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2023

Component Testing Report Updated Oct 2, 2023 12:41 PM (UTC)

File Status Duration Passed Skipped Failed
formBuilder/ArrayInput.spec.tsx ✅ Passed (Inspect) 9s 3 0 0
formBuilder/inputs/PortableText/Annotations.spec.tsx ✅ Passed (Inspect) 9s 3 0 0
formBuilder/inputs/PortableText/Decorators.spec.tsx ✅ Passed (Inspect) 10s 6 0 0
formBuilder/inputs/PortableText/Input.spec.tsx ✅ Passed (Inspect) 13s 9 0 0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx ✅ Passed (Inspect) 47s 18 0 0
formBuilder/inputs/PortableText/Styles.spec.tsx ✅ Passed (Inspect) 10s 6 0 0
formBuilder/inputs/PortableText/Toolbar.spec.tsx ✅ Passed (Inspect) 6s 3 0 0

Copy link
Contributor

@ninaandal ninaandal left a comment

Choose a reason for hiding this comment

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

lgmt 🚀

@bjoerge bjoerge added this pull request to the merge queue Oct 2, 2023
Merged via the queue into next with commit aab85f9 Oct 2, 2023
@bjoerge bjoerge deleted the sdx-730 branch October 2, 2023 14:50
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