[SPIKE] Option 2 for handling ember-a11y-refocus styles
#3251
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5 tasks
shleewhite
force-pushed
the
chore/upgrade-ember-a11y-focus
branch
from
b01d049 to
8893776
Compare
shleewhite
changed the title
ember-a11y-refocus styles
zamoore
force-pushed
the
chore/upgrade-ember-a11y-focus
branch
from
5ecdbb7 to
2621b9b
Compare
zamoore
force-pushed
the
main-5.0.0
branch
2 times, most recently
from
5fc6964 to
5ef8b4f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📌 Summary
This is related to #3234
In this option, we don't export the
ember-a11y-refocusstyles so the consumer has to include the path in theirember-cli-buildand add it as a dependency. This approach is similar to how the tokens styles work.This would require all consumers to update their
ember-cli-buildfile and we'd have to change the guidance on our website. If you don't do this, the design system package builds fine, but the showcase fails to build because it does not have access to the stylesheet.