feat: allow returning error from adlib actions in blueprints

[anteeek]

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

• I have added one or more unit tests for this PR
• I have updated the relevant unit tests
• No unit test changes are needed for this PR

Affected areas

Blueprints integration

Time Frame

Other Information

Status

• PR is ready to be reviewed.
• The functionality has been tested by the author.
• Relevant unit tests has been added / updated.
• Relevant documentation (code comments, system documentation) has been added / updated.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

❌ Patch coverage is 40.47619% with 25 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
meteor/server/api/rest/v1/playlists.ts	0.00%	25 Missing ⚠️

📢 Thoughts on this report? Let us know!