Fiori Tree Views towards GA

[danjoa]

No description provided.

[David-Kunz]

Also for @Aggregation.RecursiveHierarchy?

[danjoa]

Yes, if we replace that by a simplified shortcut, e.g. like that:

annotate AdminService.Genres with @Fiori.TreeView #GenreHierarchy .via: parent;
annotate AdminService.Genres with @Fiori.TreeView #GenreHierarchy { via: parent };

If there's only one Association to self:

annotate AdminService.Genres with @Fiori.TreeView #GenreHierarchy;

[danjoa]

CoPilot just did that for me in d46956d

[danjoa]

P.S. We can also use the loaded event instead of compile.to.edmx, e.g. in case the latter event is too late in these experiments. The final solution will anyways be baked into the compiler. Reason I started with that is that I wanted us to detect, which parts are required for EDMX only, and which are required in the runtime, or in db.

[danjoa]

Here I also tried changing Int64 types to Int16 as discussed → seems to work end-to-end for Fiori clients.

[danjoa]

Leftover: We also need to check and document how to do Value Helps:

cloud-cap-samples/fiori/app/admin-books/fiori-service.cds

Lines 70 to 81 in 987611b

	annotate AdminService.Genres with @UI: {
	PresentationVariant #VH: {
	$Type : 'UI.PresentationVariantType',
	Visualizations : ['@UI.LineItem'],
	RecursiveHierarchyQualifier: 'GenreHierarchy'
	},
	LineItem : [{
	$Type: 'UI.DataField',
	Value: name,
	Label :'{i18n>Name}'
	}],
	};

[agoerler]

We should capture these as a reusable aspect. Unfortunately, an aspect can't have virtual or computed elements.