Allow optional requiredFilename in ContentType schema?

Open Raphael-Gazzotti opened this issue 9 months ago • 2 comments

Based on this discussion: https://github.com/openMetadataInitiative/openMINDS_instances/pull/271#discussion_r1995657300_

Should we introduce an optional requiredFilename property in the ContentType schema, thus allowing instances to declare a fixed basename when truly needed (e.g., config.json, settings.json, package.json...)?

However, this property is unlikely to be broadly adopted, since most tools support customizable file names.

Apr 18 '25 07:04 Raphael-Gazzotti

I would be against doing this in the content type schema. This is targeted in a certain way with this issue #https://github.com/openMetadataInitiative/openMINDS_core/issues/522

Apr 24 '25 11:04 lzehl

@apdavison @olinux would you agree?

Apr 24 '25 11:04 lzehl