-
-
Notifications
You must be signed in to change notification settings - Fork 38
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: remove ember-prism in favour of ember-shiki #112
Conversation
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.
The failing test can be fixed by ignoring the rule (a false positive imo, one that happens easily):
await a11yAudit({
rules: {
'scrollable-region-focusable': {
enabled: false,
},
},
});
Should be fixed in |
@IgnaceMaes I wasn't able to run the app locally. Could you check what happened? App is being served by FastBoot
ReferenceError: fetch is not defined
at buildSandboxGlobals (/ember-octane-vs-classic-cheat-sheet/config/fastboot.js:7:16)
at EmberApp.buildSandbox (/ember-octane-vs-classic-cheat-sheet/node_modules/fastboot/src/ember-app.js:120:19)
at EmberApp.buildApp (/ember-octane-vs-classic-cheat-sheet/node_modules/fastboot/src/ember-app.js:152:24)
at /ember-octane-vs-classic-cheat-sheet/node_modules/fastboot/src/ember-app.js:139:22
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async EmberApp.getNewApplicationInstance (/ember-octane-vs-classic-cheat-sheet/node_modules/fastboot/src/ember-app.js:209:17)
at async EmberApp._visit (/ember-octane-vs-classic-cheat-sheet/node_modules/fastboot/src/ember-app.js:240:9)
at async EmberApp.visit (/ember-octane-vs-classic-cheat-sheet/node_modules/fastboot/src/ember-app.js:325:7)
at async FastBoot.visit (/ember-octane-vs-classic-cheat-sheet/node_modules/fastboot/src/index.js:86:18)
at async /ember-octane-vs-classic-cheat-sheet/node_modules/fastboot-express-middleware/src/index.js:33:20 Is FastBoot somehow a dependency of |
It's because the fastboot implementation uses I've reverted to Node 16 and installed |
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.
Thank you! Here's a followup issue for tracking implementing the TS examples for the user experience: #113 |
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.
I like this step towards showing TS examples! I found one blocking issue. Can we try using a different color scheme? Previously, this app had 100% Lighthouse accessibility score, but there are 2 issues:
- copy button lacks an accessible name. Do we have a way to fix that button name, maybe upstream?
- the color contrast for this theme is too low, looks like specifically the light blue is a problem. Is there another theme we can use that will pass? Or maybe drop the syntax highlighting by file type in cases where the light blue shows up (like cli commands)
This brings the score down to 87%. Across our apps, we strive for meeting AA level accessibility criteria.
To re-run these tests, go to Chrome developer tools, choose "Lighthouse" and select the Accessibility option. Then click "Analyze page load." Sorry this isn't represented in CI tests! Let me know if you need any help.
Thanks for the review @jenweber.
I haven't checked support of other themes so if anyone wants to try a different one, please go ahead! |
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.
Awesome, thank you for the a11y fixes!
@IgnaceMaes @jenweber The deployment of the app seems to have failed because |
Oops, taking a look. |
Found the issue. It's because Prember only started loading the I'll open a PR to upgrade the dependency in a sec. |
Edit - as I was typing, @IgnaceMaes opened a PR! Thank you! Just in case it's still useful somehow... I'm a little surprised to see this error, since both ember-fetch and node-fetch are present. Debugging:
|
After merging #115 the deploy succeeded. Thanks again @IgnaceMaes |
No description provided.