Make ParseSlashCommand find commands anywhere in string and return found boolean #117
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.
ParseSlashCommandrequired commands to start with/and returned errors when not found. Now it searches anywhere in the input string and returns a boolean indicating presence instead of erroring.Changes
(taskName string, params map[string]string, found bool, err error)-foundboolean positioned before error and after paramsstrings.Index()to find/anywhere in input, not just at start\nor\r) rather than consuming entire stringfound=falsewhen no command present; errors only for malformed syntax (unclosed quotes)Example
Text before the
/and after newlines is ignored as expected.Test Coverage
Added 6 test cases covering commands embedded in text, with prefixes, and newline handling. All 26 tests pass.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.