[EXTDAM-337] BynderAssetProvider should throw defined exceptions with invalid itemKey Created: 19/Jan/22  Updated: 26/Aug/22

Status: Open
Project: External DAMs
Component/s: None
Affects Version/s: 1.1.1
Fix Version/s: None

Type: Bug Priority: High
Reporter: Chuong Doan Huy Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones EXTDAM-333 S3AssetProvider should throw defined ... Closed
dependency
is depended upon by MGNLREST-256 AssetReferenceResolver throws an exce... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: AuthorX Maintenance
Team: AuthorX

 Description   

When REST module use BynderAssetProvider to get asset, but input invalid/broken assetKey (this is very common):

EXPECTED behavior : BynderAssetProvider should throw defined exceptions

CURRENT behavior : Not throw anything, return null

This lead to further code using that Asset and get exceptions


Generated at Mon Feb 12 01:54:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.