Code Quality: Move `PanelTypes` from `design-system`
See original GitHub issueTask
As discussed in https://github.com/GoogleForCreators/web-stories-wp/pull/10452#issuecomment-1060435885, PanelTypes
shouldn’t be in the design-system
package.
Alternatives Considered
Additional Context
https://github.com/GoogleForCreators/web-stories-wp/pull/10452
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
Code Quality - GitLab Documentation
Code Quality Widget. Moved to GitLab Free in 13.2. Going a step further, GitLab can show the Code Quality report right in the...
Read more >DesignSystems.com
Design & Development. Collaborations in code ; Schema by Figma. Talks and conversations ; Operations. Process & People ; Getting Started. Best in...
Read more >Design Systems Handbook - DesignBetter
Documentation helps promote those new patterns, reduce the need to write new code, and makes implementation easy with code examples and guidelines.
Read more >Best practices for building a design system - Enonic
You should have an established design process, which standardizes documentation, hand-off, code review, and quality assurance. A design system ...
Read more >Contribute - Pluralsight Design System
We want to make it easy to move between packages in the Design System, and following ... Every code submission requires a review...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah you’re right; dang I did not realize that.
After #11096 we can now theoretically just move the
PanelTypes
tostory-editor
again (making it a dependency ofelement-library
.