-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Web-components: Fix CSS class usage in CLI template #17702
Conversation
Styles are applied to the element when the attribute is `class`, not `className`.
Mimic the attribute change made and tested on the respective `.js` file: 2daf62c
☁️ Nx Cloud ReportCI is running/has finished running commands for commit f1d39bc. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
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.
Hey @tacc-wbomar thanks for your contribution!
Sorry about the pipeline failures, we are facing an issue with E2E tests with pnp for Vue and React, and that is not related to your changes. Thanks for checking!
The change you made is related to CLI templates used to bootstrap new projects. In Chromatic we use the kitchen sink app which is not related to the change you made, hence it didn't introduce changes. It's all good! |
Thank you. I've injected "Update: " statements into this PR desc and my issue that will clarify my inaccuracy to others and point to your comments as resolutions. |
Web-components: Fix CSS class usage in CLI template
Issue: Styles were not being applied to an element using attribute
className
.What I did
Change
.js
file'slit-html
markup to useclass
attribute instead ofclassName
.How to test
Does this need a new example in the kitchen sink apps?No "Jest or Chromatic screenshots". I tried.
StorybookI failed: #17703Edit: I found Chromatic runs automatically. It is recorded as having passed, and though I agree
, I think it is a broken test.1Update: I was ignorant of the complexity and feature set of the Storybook pipelines. See #17702 (comment).
Footnotes
I found the relevant test suite ("regression-test-webcomponents"). The relevant stories ("Example" > "Page") do not reflect my change. I see
classname
is still used, and styles are still not applied. I don't understand the purpose of this automation. ↩