-
Notifications
You must be signed in to change notification settings - Fork 172
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
Split out execute errors that come from authenticated calls #3589
Comments
Complexity: 13 Powered by Parabol |
Impact: 4 Powered by Parabol |
Urgency: 3 Powered by Parabol |
Complexity: 13 Powered by Parabol |
Impact: 3 Powered by Parabol |
Urgency: 3 Powered by Parabol |
Problem
Auth check calls will fall under the generic Execution Failure and this will bubble up to the UI. Ideal case is all integrators use a standard
onlySource
modifier that fails with a standard error message. Then we can parse out this message and show authenticated executes as "Pending Authentication" (or something) in the UI.Proposed Solution
onlySource
modifier: subtask in Export an interface-only module so it's easier to dev with #3457The text was updated successfully, but these errors were encountered: