FLOW-1757: handle slash command errors as warnings#1688
Open
ccallcottstevens wants to merge 3 commits intomainfrom
Open
FLOW-1757: handle slash command errors as warnings#1688ccallcottstevens wants to merge 3 commits intomainfrom
ccallcottstevens wants to merge 3 commits intomainfrom
Conversation
Contributor
|
The issue is ready for review, and the acceptance criteria have been met:
|
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
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.
What Is This Change?
This is a copy of this pr: #1649 that couldn't be merged because it was written by Rovo Dev.
It's purpose is to handle InvalidPromptError unknown slash errors as warnings instead of errors.
How Has This Been Tested?
Basic checks:
npm run lintnpm run testAdvanced checks:
Recommendations:
Rovo Dev code review: Rovo Dev is reviewing this pull request…
Refresh the page in a few minutes to see the results.