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

nimble-wafer-map Component #924

Open
29 of 37 tasks
nate-ni opened this issue Dec 15, 2022 · 1 comment
Open
29 of 37 tasks

nimble-wafer-map Component #924

nate-ni opened this issue Dec 15, 2022 · 1 comment
Labels
enhancement New feature or request new component Request for a new component

Comments

@nate-ni
Copy link
Contributor

nate-ni commented Dec 15, 2022

😯 Problem to Solve

💁 Proposed Solution

📋 Tasks for release readiness

Preview Give feedback
  1. bug
    arinluca333

Tasks post-release

Preview Give feedback
  1. enhancement
  2. enhancement
@nate-ni nate-ni added the new component Request for a new component label Dec 15, 2022
@nate-ni nate-ni moved this to 🏗 In progress in Nimble Design System Priorities Dec 15, 2022
@m-akinc m-akinc moved this from In progress to Defined/Ready to Pickup in Nimble Design System Priorities Apr 17, 2023
@rajsite rajsite added the enhancement New feature or request label Mar 7, 2024
@jattasNI
Copy link
Contributor

jattasNI commented Oct 1, 2024

We discussed the long term plan to move this out of incubating as part of #2406. The proposal there is that this component belongs in the Spright package within the Nimble repo. It's not a reflection of the quality, completeness, or usefulness of the component, just that it is more special-purpose than typical Nimble components like text field and table.

The work involved would be to move the code from packages/nimble* to packages/spright* and move the stories to the Spright section of storybook. This would be a breaking change for clients as they would now import from spright-angular, SprightBlazor, or spright-components packages. We'd need to either update client apps or notify them to make the updates themselves.

@munteannatan @DStavilaNI What do you think of this proposal? If you like the direction, any chance your team would be interested in implementing that migration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new component Request for a new component
Projects
Status: Defined/Ready to Pickup
Development

No branches or pull requests

3 participants