getkirby
Blueprint options: Indicate if prop accepts query syntax
It would be great if blueprint options had indicators if a property supports query syntax or not. Some do, some don't, and currently we always have to go to the source code or find out by trial and error.
I guess we would have to fix this partially in the core, e.g. for field props. Just adding something like (support query syntax). There are likely other parts that are manual docs that we would need to treat as well.
I guess we would have to fix this partially in the core, e.g. for field props.
Yes, I thought so. Should I add another issue in the core repo?
I think it's fine here. We can look at it for 3.6.1 or 3.6.2 - shouldn't be too difficult to do
How's the rule for custom docblock comments? Couldn't we just make up our own? Something like
/**
* @queries true
*/
Our parser can parse all that stuff as far as I know.
This would also make our lives a lot easier for the blueprint editor.
We should be able to implement this custom docblock tag in our reference models.
Maybe it would be cool to create a general concept for such custom tags. What would be useful for the docs and what would be useful for the editor?
The @queries tag should also be able to differentiate between props that are a query themselves and props that may use queries with the {{ }} syntax.
@lukasbestle true, I'm just not sure how - I think this already causes some headache with users. We should find a way/words that convey the difference easily
We could use a more generic tag like:
@string-type query
@string-type query-template
@string-type html
@string-type markdown
@string-type query-template html // combination of both
...
Open for a better name. :)