rusackas opened a new pull request, #37771:
URL: https://github.com/apache/superset/pull/37771

   ## Summary
   
   Eliminates the `superset-ui-demo` package and consolidates all Storybook 
stories to be co-located with their source code. This simplifies the monorepo 
structure and follows modern Storybook best practices.
   
   ### What Changed
   
   **Package Removed:**
   - Deleted `packages/superset-ui-demo/` entirely (~16,670 lines removed)
   
   **Stories Migrated (84+ files):**
   - Plugin stories → `plugins/*/src/stories/` (co-located with source)
   - Core package stories → `packages/superset-ui-core/src/*/stories/`
   - Shared utilities → `.storybook/shared/` with `@storybook-shared` webpack 
alias
   
   **Config Updates:**
   - `.storybook/main.js` - Updated story globs and added webpack alias
   - `package.json` - Removed `plugins:storybook` and `plugins:build-storybook` 
scripts
   - `.github/workflows/superset-frontend.yml` - Removed plugins storybook 
build step
   
   **Cleanup (bonus housekeeping):**
   - Removed 7 stale dependabot entries for non-existent plugins (histogram, 
sankey, event-flow, sankey-loop, preset-chart-xy, heatmap, sunburst)
   - Added 2 missing dependabot entries (plugin-chart-ag-grid-table, 
plugin-chart-cartodiagram)
   - Removed demo package references from `.eslintrc.js`, `jest.config.js`, 
`check-custom-rules.js`
   
   ## Test Plan
   
   - [x] `npm run build-storybook` completes successfully
   - [x] All stories are discoverable in the consolidated Storybook
   - [ ] CI passes
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to