[EXTDAM-149] External asset providers don't respect queries Created: 04/Sep/20  Updated: 26/Aug/22

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

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Date of First Response:
Epic Link: AuthorX Maintenance
Team: AuthorX

 Description   

Steps to reproduce

  1. Easier to reproduce on M6.2.3 (dam link field converter now uses aggregated asset provider, or on older version use new framework dialog)
  2. With and external dam (Bynder, S3)
  3. Open an asset link field.
  4. Use column filters

Expected results

All assets are filtered

Actual results

Only JCR assets are filtered.

Development notes

External providers don't respect queries in info.magnolia.dam.api.AssetProvider#list



 Comments   
Comment by Jesus Alonso [ 07/Sep/20 ]

The query is not using keyword for filtering (as I was expecting) but something like:

properties = “name” -> “moon”

Where name is the name of the column and moon the text entered.

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