Open damonsk opened 4 years ago
@damonsk have you thought of a syntax for this? This is a convex hull problem, in which given a set of points we can draw a shape that encompasses those points. The LOOK of the shape can be an issue, but I feel like for this OWM language, dropping poly coordinates is an anti-pattern?
Since it can be defined by a set of points, seems like it could be a scope, or a set, or both. A simple version could be a scope, e.g.:
interest <opts> {
component One
component Two
}
Simple to see, but limits components to being in only one area.
Can treat it as a set of declaratively:
area [Comp1, Comp2, ...]
I think it is important to be able to have components being in multiple areas of interest. In most of the maps I've had to work through, components often end up in multiple areas of interest.
My suggestion into the mix is,
interest <opt> [Comp1, Comp2, ...]
or for better readability,
interest <opt> [
Comp1,
Comp2,
... ]
BTW, just curious as to where is this enhancement in the backlog?
As per https://miro.medium.com/max/5496/1*4exsrh6Ju8wFr6DEHkUTQw.jpeg
'An area of interest, something worth noting, e.g components designated to a team.'
Parent #51