feat: allow returning error from adlib actions in blueprints#1638
feat: allow returning error from adlib actions in blueprints#1638anteeek wants to merge 2 commits intoSofie-Automation:mainfrom
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
b2484b1 to
545404c
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
About the Contributor
This PR is made on behalf of the BBC
Type of Contribution
This is a:
Feature
Current Behavior
Currently, there's no way to return a meaningful error message (other than just 500 - failed) from running an adlib action
New Behavior
This PR adds a method that allows to return a meaningful error message as to why an action has failed due to user error (it's meant for expected errors, exceptions are still a valid exit point for method and still will be handled as-is)
Testing
Affected areas
Blueprints integration
Time Frame
Other Information
Status