-
Notifications
You must be signed in to change notification settings - Fork 77
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
feat: calcite-design-tokens in monorepo package #7621
Conversation
This reverts commit 348f22d. # Conflicts: # tokens/component/stepper-item.json
chore: updating my branch with the latest from main
also include links
…calcite-components into astump/7180-design-tokens-in-monorepo
e43ed45
to
457b5eb
Compare
…calcite-components into astump/7180-design-tokens-in-monorepo
…calcite-components into astump/7180-design-tokens-in-monorepo
"patch:ssr": "ts-node support/patchSSR.ts", | ||
"tsc": "tsc" |
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.
Can you undo this change? I'm not sure why Stencil created an npm script for tsc
in their example, but I'd like to do some tests before removing it, since it's not related to this PR.
Let's keep unrelated changes in separate PRs, especially when they are for different packages in the monorepo
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.
There's quite a bit of changes unrelated to the monorepo move that I think need to be split up into separate PRs (e.g., wiring up of additional tokens, modifying the React wrapper build, package script order, renamed tokens, addition of global). IMO, the extent of those changes are risky to add for today's release.
@alisonailea @benelan Let's sync up first thing tomorrow about this.
Related Issue: #7180 #7325
Summary
This pulls the Calcite-Design-Token repo (with commit history) into the Calcite-Design-System Monorepo.