|
The ticket is about adding some sort of sugar to allow for Type[title] style querying of resource related data.
In dalen's old query facility, he had Type[title] as a first class way of matching resources. This is one way to fix this problem:
Another way is to provide a model change that exposes the combination as a string field for matching, for example:
resources { resource = "Class[foo]" }
|
Or something like that? Either way, we need to make a decision on some sugary syntax for this, and have it apply to anywhere where resources are referenced, right now this is `resources` and `events` I believe, possibly also `resource-statuses` but thats an interesting case to debate over.
The output of this ticket should be a design proposal with socialisation, and tickets to implement the agreed idea.
|
