fix: display MCP tag for prompts in autocomplete but not in prompt #6531
+8
−2
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.
A last-minute change from @rekram1-node in #5767 was to add an
(MCP)tag to the name of the prompt if it was an MCP one. Quite a nice addition to be fair. However, that broke the functionality because now the prompt has a space, meaning the(MCP)part is considered an argument by the parser and the name is not matched.This PR fixes it by adding an
mcpproperty to theCommandobject so that we can still display the(MCP)tag but then when it's added to the prompt only the uninterrupted name is there which mean the substitution will work fine.One possible change could be to have a general
tagproperty instead of the specificmcpone so that if we want to add more tags in the future we can for example display/my-command (CUSTOMTAG)...but it might be surperflous.