docs: add stories for how PrismFormatted handles long lines #319
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 tasks
huyenltnguyen
commented
Sep 16, 2024
Comment on lines
+90
to
+97
| decorators: [ | ||
| (Story) => ( | ||
| <details> | ||
| <summary>Example code</summary> | ||
| <Story /> | ||
| </details> | ||
| ), | ||
| ], |
There was a problem hiding this comment.
I'm using the decorators option to render <PrismFormatted {...props} /> with extra stuff.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist:
Update index.md)I was tweaking PrismFormatted storybook examples to check if the changes in freeCodeCamp/freeCodeCamp#56119 should be ported over (in other words, if the issue is in PrismFormatted or just in /learn). And since I already made the storybook changes, I thought I should just check them in since they could be useful for sanity check.
The two examples I'm adding are:
PrismFormattedreceives a long stringPrismFormattedreceives a long string, and the component is rendered inside adetailselementIn both cases, the string is rendered as a single line and doesn't wrap (as we expect), so I think the issue isn't in the PrismFormatted component.
Screenshot
Screenshot