Skip to content

Deployment shapes should actually be arbitrary filters #1098

@DanySK

Description

@DanySK

There is no real reason for shapes to be the only way to determine node contents. Indeed, whether or not some content should be injected is more generally the result of a predicate p of kind (RandomGenerator, Environment, Node) -> Boolean. Current Shapes are just a particular case where this predicate is actually somewhat like: p = { (_, env, node) -> shape.contains(env.getPosition(node)) }.

A more general concept of SubDeploy or ContentFilter should be used instead, with Shapes re-implemented as subclasses.
Also a special ContentFilter could reuse the JSR223 infrastructure and allow for full-fledged scripts to be executed.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions