Connectors redraw on resize

[bjoerge]

Type of change (check at least one)

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (fix or update to documentation)
• Maintenance
• Other, please describe:

Does this change require a documentation update? (Check one)

• Yes
• No

Current behavior

Currently the connector lines are not redrawn/recalculated on resize.

Description
This makes sure the connector lines are being redrawn properly on window resize.

There are three separate commits that can be reviewed individually:

• a9718b8 Exports a single resizeObserver instance that can be shared across different studio components (there are performance gains to be had from using a single instance instead of creating multiple). It's also exported with a bit nicer API that fits React hooks a bit better than the native ResizeObserver API.
• 4825c6c Makes desk-tool import the shared resizeObserver instance from base instead of creating its own.
• 55e0e5f Makes use of the same resizeObserver instance to force redraw the connector lines on resize.

Note for release
Fixes an issue with lines connecting a change with it's corresponding input not being redrawn on window/pane resize.

Checklist

• I have read the Contributing Guidelines
• The PR title includes a link to the relevant issue
• The PR title is appropriately formatted: [some-package] PR title (#123)
• The code is linted
• The test suite is passing
• Corresponding changes to the documentation have been made

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/sanity-io/test-studio/h64fqcxkw
✅ Preview: https://test-studio-git-connectors-redraw-on-resize.sanity-io.vercel.app

[benedicteb]

Looks good to me :)

Only thing I'm thinking of is perhaps moving the resize observer stuff somewhere more general where more things can use it?

[bjoerge]

Only thing I'm thinking of is perhaps moving the resize observer stuff somewhere more general where more things can use it?

Yep, we can consider that. Not sure yet if this should be part of our public API, so I think we can live with importing it from @sanity/base/lib/util (as we do in desk-tool for now).

Thanks for reviewing!