Valid ViewsMetaData.json location?

[trendoid]

It looks like from the extended-content-list sample that the field mapping occurs in `Views/Shared/Components/SitefinityContentList/ViewsMetaData.json but there is also a ViewsMetaData.json file in the resource-package-minimal sample.

The only location that seems to work is in the Views/Shared/Components/SitefinityContentList/ViewsMetaData.json file.

Changing ResourcePackages/Minimal/Views/Shared/Components/SitefinityContentList/ViewsMetaData.json doesn't do anything.

Is this as intended? Can the useless file be removed? Or is this a bug? Can Resource Packages also have custom field mapping?

[Gebov]

Hello,

IMO the ViewsMetadata.json file should work per package since the views are specific to that package. The primary location (Views/Shared/Components/SitefinityContentList/ViewsMetaData.json) currently is used to override the default package we ship(Bootstrap), but it should be secondary if there is ViewsMetadata.json file for that specific package. We will log it as a bug

[trendoid]

@Gebov Thanks. The team here and our service delivery partner agree with you on that. Thanks for submitting it as a bug.