-
Notifications
You must be signed in to change notification settings - Fork 14
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
chore(PPDSC-2369) fix DOM errors in docs website #343
Conversation
You can preview these changes on: |
|
||
*/ | ||
|
||
export const UnpackContent = ({ |
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.
Shall we leave a comment about what this component does? I think the name is not very descriptive and the explanation you left in the PR description was useful, I think would be good to an explanation it in code too
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.
Agree, would also be good to explain why as well as what.
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.
Added comment
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.
Thanks! The example looks good!
I wonder if would be beneficial to add why we are also doing this? now makes sense but in the long term we have no documentation about this component which is quite unique 🤔 . Also thinking in case we need to re-use it for new implementations
It's big changes. Thanks Stoyan 👍 Looks good to me. I keep eye on it, if I found any I keep you posted. Well done! |
7521b79
* chore(PPDSC-2369): fix dom errors in theme pages * chore(PPDSC-2369): add react keys * chore(PPDSC-2369): change all components * chore(PPDSC-2369): change all components * chore(PPDSC-2369): update unpack content * chore(PPDSC-2369): clean up * chore(PPDSC-2369): format code * chore(PPDSC-2369): add key to media-list * chore(PPDSC-2369): fix unordered-list usage * chore(PPDSC-2369): fix unit tets * chore(PPDSC-2369): add as option to flag component * chore(PPDSC-2369): update snapshots * chore(PPDSC-2369): add unit tests * chore(PPDSC-2369): fix types * chore(PPDSC-2369): feedback * chore(PPDSC-2369): add prod check for nested divs outline * chore(PPDSC-2369): fix some spacing * chore(PPDSC-2369): fix unit tests * chore(PPDSC-2369): rename fns * chore(PPDSC-2369): add extra description * chore(PPDSC-2369): fix some pages * chore(PPDSC-2369): fix snapshots * chore(PPDSC-2369): fix story
PPDSC-2369
What
Background - prevent validateDOMNesting errors
What did you do:
2.1. Refactored all docs pages where we use wrong nested elements
2.2. Added global CSS style which will easily outline feature errors
2.3. Created UnpackComponent which checks its children and wraps them in TextBlock when is needed
What does the reviewers should expect
I have done:
I have tested manually:
Before:
After:
Who should review this PR:
How to test: