fix(pagination): remove incorrect nested li from pagination link #2190
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
|
@takeshikriang is attempting to deploy a commit to the shadcn-pro Team on Vercel. A member of the Team first needs to authorize it. |
|
Someone please merge this, thanks. |
…rom-pagination-link
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This was referenced Jan 18, 2024
Closed
|
Great, thanks. |
takeshikriang
deleted the
fix(pagination)/remove-incorrect-nested-li-from-pagination-link
branch
kjxbyz
pushed a commit
to muse-ui/muse-ui
that referenced
this pull request
Jun 7, 2024
…dcn-ui#2190) * feat: remove PaginationItem * chore: build registry --------- Co-authored-by: shadcn <[email protected]>
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.
I got this error from Next.js 14 telling about a
<li>nested insied<li>on Pagination component.