-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[ui] Move CodeMirror-based components out of main ui-components export #26304
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Deploy preview for dagit-storybook ready! ✅ Preview Built with commit 59d304b. |
Going to push up an additional change to fix the build. |
a33571a
to
aab3109
Compare
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit 59d304b. |
2aee32e
to
45160d8
Compare
format: 'cjs', | ||
sourcemap: true, | ||
{ | ||
input: './src/editor.ts', |
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.
NIce!
[INTERNAL_BRANCH=dish/plus-components-editor]
45160d8
to
59d304b
Compare
dagster-io#26304) ## Summary & Motivation The CodeMirror-based components in `ui-components` are adding quite a bit of CSS bloat via automatic imports, and the implicit use of `navigator` breaks static rendering in Next.js apps. Split them out into an `editor` export, which can be used via `@dagster-io/ui-components/lib/editor`. It would probably be good to split the library up further, but this is at least a step in the right direction. ## How I Tested These Changes TS, lint, jest. `yarn build` for the component library, verify that it builds correctly and that CM-based components are split out of `index`.
Summary & Motivation
The CodeMirror-based components in
ui-components
are adding quite a bit of CSS bloat via automatic imports, and the implicit use ofnavigator
breaks static rendering in Next.js apps.Split them out into an
editor
export, which can be used via@dagster-io/ui-components/lib/editor
.It would probably be good to split the library up further, but this is at least a step in the right direction.
How I Tested These Changes
TS, lint, jest.
yarn build
for the component library, verify that it builds correctly and that CM-based components are split out ofindex
.