feat: components v2 #10781
Open
feat: components v2 #10781
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
Qjuh
requested review from
vladfrangu,
kyranet and
SpaceEEC
and removed request for
a team
Qjuh
force-pushed
the
mainlib-v14/v2-components
branch
from
e6541fb to
8835fd6
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
imnaiyar
approved these changes
Feb 27, 2025
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.
Please describe the changes this PR makes and why it should be merged:
Implements Components v2 into mainlib v14.
Only raw JSON data is supported yet, builders not included.
Depends on
Will need a builders v1 release too, since that discord-api-types PR is breaking and some types builders use have been renamed. But since builders v1 is on another branch it has to be another PR.
TODO: uncomment the currently commented type tests that fail because of wrong builders version once builders PR is done, merged and released; also bump builders version to that release.
Status and versioning classification: