[MGNLDAM-1045] Include "allowedNodeTypes" property on AssetDatasourceDefinition Created: 20/Jun/22  Updated: 26/Aug/22

Status: Open
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Roberto Gaona Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
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)
Date of First Response:
Epic Link: AuthorX Support
Team: AuthorX

 Description   

At the current moment, AssetDatasourceDefinition is missing the allowedNodeTypes, which doesn't allow clients to set a filtering on the selectable node types.



 Comments   
Comment by Roman Kovařík [ 20/Jun/22 ]

Can we ask the customer about the use case?

The example from the linked ticket:

$type: damLinkField
  datasource:   
    $type: assetDatasource
    rootPath: /terms-and-conditions
    workspace: dam
    allowedNodeTypes:  
      - mgnl:asset //what does this mean? there are no other nodetypes for JCR assets
Comment by Adolfo Rodriguez [ 22/Jun/22 ]

Instead of introducing technical debt (that can be ok as a workaround), it looks more consistent, for the long term, to follow for assetDatasource the same configuration that jcrDatasource is doing, is not it?

allowedNodeTypes
optional
List of node types the data source operates on. If no value is specified, the data source will operate on all node types.

https://docs.magnolia-cms.com/product-docs/6.2/Apps/App-configuration/Data-source-definition/JCR-data-source.html#_list_of_properties

Generated at Mon Feb 12 05:05:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.