Open hlanderdev opened 1 year ago
Quick Correction: It should be "type": "component" not "type": "components". My mistake.
I caught that too, was thinking maybe we want to handle plurals for schema types (in addition to singular). Not sure if it's a bad practice to allow either way to work, but I have to remind myself every time which to use.
Feature Request
Currently a "components" type in _schema.json looks like this:
A * Catch All feature could be useful here especially if you have a good component naming convention. For example, given the components: "resources_hero", "resources_section", and "resources_blah"; You could have a _schema.json file like this:
That would include all of those components, as well as any future components that follow that convention.