-
Notifications
You must be signed in to change notification settings - Fork 203
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
Issue #2320 - Adds wc-Comment-content-nsfw to new CSS #2648
Conversation
@marimeireles thanks. The logic of nsfw is back. In the issue #2320 there are two purposes.
You did the first step, but no the second step. So you have to update the className in the css file and the js file to be consistency with the classNames |
Is the style we should be using documented somewhere @magsout? I'm not sure I even know. :)) |
Good question @miketaylr and I would say, no. It's just about feeling of what kind of component you're coding and/or where you're adding properties. It's very subjective so I think it would be nice to document that. For this issue, I would say something like : |
@miketaylr Thanks for the question. I followed your recommendation in this new pr. |
My bad, I should have been more specific. Perfect for the css part 👍 good job. Just one thing and after that i think we can merge, we need to update className in JS files :
then same thing for all className
|
Sorry for taking so long and forgetting to change on the other files! :( |
@marimeireles awesome. Good job, and thanks a lot. |
This PR fixes issue #2320
It's necessary to add a
nsfw
label to the github repository in order for these changes to work.r? @magsout