Add richMenuAliasId Support and Improve Parameter Descriptions in createRichMenu Tool #145
Conversation
This file contains hidden or 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
…ru/generate-rich-menu
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.
Add
richMenuAliasIdSupport tocreateRichMenuToolOverview
This PR adds support for creating and updating a rich menu alias in the
create_rich_menutool, enabling seamless switching between rich menus.Additionally, it includes a minor refactor for the
getMessageQuotatool.Changes
createRichMenu.tsrichMenuAliasIdparameter to thecreate_rich_menutool.richMenuAliasIdis provided, the tool will delete any existing alias with the same ID and create a new alias linked to the newly created rich menu.actionsparameter to provide more detail.richMenuAliasResponsein both the error and success responses for better traceability.getMessageQuota.ts