Skip to content

Component css packages #2

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

Closed
wants to merge 18 commits into from
Closed

Conversation

snowystinger
Copy link
Member

Closes

✅ Pull Request Checklist:

  • Included link to corresponding Issue.
  • Added/updated unit tests and storybook for this change (for new code or code which already has tests).
  • Filled out test instructions.
  • Updated documentation (if it already exist for this component).
  • Looked at the Accessibility Standard and/or talked to @mijordan about Accessibility for this feature.

📝 Test Instructions:

Everything should still work as expected and CSS should be pulled from @adobe/spectrum-css unless we're overriding it in which case it should take it locally from @adobe/spectrum-css-temp/components

🧢 Your Team:

Copy link
Member

@devongovett devongovett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! How do we verify that all our changes and their changes got synced properly?

@snowystinger
Copy link
Member Author

@devongovett I haven't merged any of our changes in their direction or theirs in ours. For components where we made a change, I kept that, for ones we haven't changed yet, i use their directly and when we need to make changes, we'll override it locally at that point

As for how to make sure everything is still working, since we don't have chromatic yet, i suppose we'll need to verify manually

@snowystinger snowystinger force-pushed the component-css-packages branch from 1d791f6 to ba70abc Compare October 1, 2019 19:54
@@ -17,3 +17,4 @@ storybook-static

#allow
!.storybook-v3/lib
!packages/**/dist
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pay attention, needed for spectrum-css, not necessarily anything else, 🤷‍♂ ?

@github-actions
Copy link

github-actions bot commented Oct 5, 2019

Build successful! View the storybook

@github-actions
Copy link

Build successful! View the storybook

@github-actions
Copy link

Build successful! View the storybook

@snowystinger snowystinger force-pushed the component-css-packages branch from 3384a02 to 6b0cbed Compare October 11, 2019 17:23
let scales = getVariableMappings(['large', 'medium']);
let globals = getVars('packages/@adobe/spectrum-css-temp/vars/spectrum-global.css');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you're using individually versioned components, you can refer to @spectum-css/vars/dist/spectrum-global.css. It won't be as paired down as the -unique, but it will have all the variables that a newly added component may use. If you use -unique, you'll only ever get the variables used by the versions of the components that are specifically in that bundle release. If you add a new component or update a component to a version greater than what is in the bundle you're referencing, you might have missing variables.

@snowystinger snowystinger deleted the component-css-packages branch November 13, 2019 01:07
snowystinger added a commit that referenced this pull request May 3, 2021
LFDanLu added a commit that referenced this pull request Sep 2, 2021
majornista added a commit to majornista/react-spectrum-v3 that referenced this pull request Feb 14, 2022
majornista added a commit to majornista/react-spectrum-v3 that referenced this pull request Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants