Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to manage errors? #797

Closed
lucafx opened this issue Dec 22, 2022 · 3 comments
Closed

How to manage errors? #797

lucafx opened this issue Dec 22, 2022 · 3 comments
Labels
auto-triage-stale question Further information is requested

Comments

@lucafx
Copy link

lucafx commented Dec 22, 2022

Hello everybody,

I'm using this FW to build a slack bot, but i don't have any idea on how to manage errors and restrictions.

There are some actions in the bot dedicated to only a part of the customers (but visible to everybody) and i'd like to do do some kind of error message describing why that action wasn't possible etc.

The only way idea that come in my mind to reach this goal is to use a modal for each different exception, but i should write a lot of different cases to manage every scenario.

Is there anything that i didn't find that can help me?

Thank you very much!

Luca

@srajiang
Copy link
Member

Hi @lucafx - Yes, a pretty common pattern we see is people updating a modal view with an error message if a user takes an action thats invalid for some business reason.

You might have a modal (view) composed of some input fields or buttons. Slack will send interaction payloads (assuming you have that configured on your app) based on the type of action, here's some basic documentation on view interaction payloads.

In response to a block_action or a view_submission or some other form of interaction payload, or you may supply an error as part of a response_action when your app acknowledges (ack()) the Slack request or if you'd like more control over how the error appears, you may also consider updating the view itself to show some blocks with an error message.

@srajiang srajiang added the question Further information is requested label Dec 22, 2022
@github-actions
Copy link

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.

@github-actions
Copy link

github-actions bot commented Feb 6, 2023

As this issue has been inactive for more than one month, we will be closing it. Thank you to all the participants! If you would like to raise a related issue, please create a new issue which includes your specific details and references this issue number.

@github-actions github-actions bot closed this as completed Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-triage-stale question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants