Skip to content

FLOW-1757: handle slash command errors as warnings#1688

Open
ccallcottstevens wants to merge 3 commits intomainfrom
FLOW-1757-Handle-bad-slash-commands-as-warnings
Open

FLOW-1757: handle slash command errors as warnings#1688
ccallcottstevens wants to merge 3 commits intomainfrom
FLOW-1757-Handle-bad-slash-commands-as-warnings

Conversation

@ccallcottstevens
Copy link
Copy Markdown
Contributor

@ccallcottstevens ccallcottstevens commented Mar 6, 2026

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 lint
  • npm run test

Advanced checks:

  • If Atlassian employee & Bitbucket changes: did you test with DC in mind? See Instructions

Recommendations:

  • Update the CHANGELOG if making a user facing change

Rovo Dev code review: Rovo Dev is reviewing this pull request…
Refresh the page in a few minutes to see the results.

@atlassian
Copy link
Copy Markdown
Contributor

atlassian bot commented Mar 6, 2026

The issue is ready for review, and the acceptance criteria have been met:

  • ✅ Bad or unknown slash commands are handled as warnings rather than raising an InvalidPromptError.
  • ✅ The 'Unknown command' InvalidPromptError no longer occurs in boysenberry when a bad slash command is received.

Check Jira issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant