Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Framework: Using the wordpress a11y package instead of the global #2425
Conversation
youknowriad
self-assigned this
Aug 15, 2017
youknowriad
requested a review
from aduth
Aug 15, 2017
aduth
requested changes
Aug 15, 2017
Should we remove the dependency here?
gutenberg/lib/client-assets.php
Lines 129 to 134 in acde984
Additionally / alternatively, we might consider how we plan to reconcile the wp-a11y script included in core currently with the now-packaged variant, and whether the two can be merged. Might be a topic for a JavaScript Office Hours discussion (cc @omarreiss)
codecov
bot
commented
Aug 15, 2017
•
Codecov Report
@@ Coverage Diff @@
## master #2425 +/- ##
======================================
Coverage 30.1% 30.1%
======================================
Files 174 174
Lines 5288 5288
Branches 907 907
======================================
Hits 1592 1592
Misses 3132 3132
Partials 564 564
Continue to review full report at Codecov.
|
|
@aduth Good catch and right, maybe this is the first package to be used from the packages repo in Core. |
|
@aduth Do you think we should merge this since the core integration won't be resolved today? |
aduth
approved these changes
Aug 25, 2017
Yes, especially since we're not clobbering the global at the moment anyways, just pulling direct from NPM.
youknowriad commentedAug 15, 2017
No description provided.