docs: Add block about styleType to List documentation
#8278
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
🦋 Changeset detectedLatest commit: 9fa7a87 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
segunadebayo
added a commit
that referenced
this pull request
May 8, 2024
…a plugin (#8310) * Fix custom font code snippet typo on nextjs-pages-guide (#8240) There's a small typo on the `_app.js` snippet for adding custom fonts with NextJS. This just fixes that to `return` the fragment instead of prefixing the fragment with a semicolon. * feat: support custom conditions / psuedo props (#8218) * chore: wip * chore: update generated conditions * docs: update changeset * feat: add new pseudos * feat(v3): remove social media colors (#8249) * refactor(v3): simplify changelog (#8253) * refactor(v3): simplify v1 changelog * refactor(v3): simplify v2 changelog * fix(deps): update dependency github-slugger to v1.5.0 (#8258) * fix(deps): update dependency @docusaurus/utils to v2.4.3 * fix(deps): update dependency github-slugger to v1.5.0 --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * docs: update edit url (#8276) * fix(deps): update dependency framer-motion to v9.1.7 (#8257) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * fix(deps): update dependency @docusaurus/utils to v2.4.3 (#8256) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * docs: Add block about `styleType` to `List` documentation (#8278) docs: add block about styleType to List documentation * feat(v3): support `asChild` composition (#8302) * feat: support as child composition * refactor: simplify types * chore: deprecate as props * refactor: rename vars * docs(website/gatsby-guide): update guide to include deprecating chakra plugin --------- Co-authored-by: Samyok Nepal <nepalsamyok@gmail.com> Co-authored-by: Segun Adebayo <joseshegs@gmail.com> Co-authored-by: Michał Korczak <michal.k2001@gmail.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Taiga KATARAO <32538736+tarao1006@users.noreply.github.com> Co-authored-by: Ivan Schedrovskiy <ltlaitoff@gmail.com>
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.
Closes #8140
📝 Description
Added to
Listdocs description aboutstyleTypeand examples how to use⛳️ Current behavior (updates)
Based on issue #8140, I understand that people need to create a clear description in the documentation of how to set custom markers using built-in CSS methods
🚀 New behavior
In the documentation, a block was created to describe the functionality of the
styleTypeproperty. I hope this will help people who encounter this issue in the future💣 Is this a breaking change (Yes/No):
No