Make Schema Work Without `blueprint` Property

[JojOatXGME]

Hi, I was trying out your schema for Kirby CMS. However, I don't want to add the blueprint property to all my blueprints. After all, these blueprints are shared with other people who don't use this schema. For this reason, I have two requests:

1. It would be nice if the blueprint property would be optional. Right now, I get the warning about the missing property.

2. To make the schema aware of the type of blueprint, I was wondering if we could create separate schemas. All the different types of blueprints are inside distinct directories. I could just configure different schemas for each directory inside my IDE.

Anyway, thanks for the current version of the Schema.

[bnomei]

the blueprint property is optional but as you noticed the schema otherwise has no way to detect whats the scope.

i agree that using multiple files (pages/files/site/fields) would solve that but they is a hassle to maintain. thank you for suggesting that, I had not considered that myself yet.

since the blueprint property will not disrupt or yield errors for those that do not have the schema installed I think its an acceptable trade off and I am not likely to add the seperate files.

side note: k6 which, given the planed release cycle will ship within the next year, will have major simplifications to the blueprint schemata as well as stronger capabilities to create blueprints via PHP. this will allow us developers to create blueprints with much more confidence and less tinkering in YAML.

[bnomei]

feel free to ship a copy of the my schema with you project repo to share it with others. the schemata almost never changes between kirby versions.

[JojOatXGME]

Thanks for the very fast response. 😲 What I meant is that the blueprint property is marked as required at various places.

kirby-schema/kirby4-blueprints.schema.json

Lines 743 to 745 in a9571f9

	"required": [
	"blueprint"
	],

I am referring to the schema for Kirby 4 because this is the schema I am using right now. I also checked the schema for Kirby 5. This causes the following warning in my editor:

Anyway, I am not sure if declaring the property as optional has any negative side effects.

side note: k6 [...] will have major simplifications to the blueprint schemata

Thanks for the info. I am relatively new to Kirby and haven't heat of that. Wondering what that means for existing blueprints.

Anyway, thanks for your work so far.