feat: support for pre-generated component json, in the same way we support pre-generated embed json #1427
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.
This adds a new method to
dpp::message
that accepts a string containing json, which can be used to pre-generate component designs at sites such as https://discord.builders in a library agnostic way.We have had ways to do this with embeds since version 1.0 and earlier, and this is used quite effectively in production bots. As such providing a facility to do the same for components makes a lot of sense, as it allows for component designs to be stored in external json files, which can be localised etc.
The new method does not parse into the object, but attaches the array as-is to the components member of the json sent, so that if there are features the lib does not support for some reason, this can be done via this new method.
Code change checklist