Miro Spönemann
Miro Spönemann
Maybe we should think about some way to put arbitrary behavior into dependencies and validation of layout options (see #15). We could do it by expecting implementations of some interfaces....
What about implementing [Proposal 1](#issuecomment-222451236) then? It's the shortest of the proposed syntaxes. > For example if a single enum value is incompatible but additional enum values are expected to...
Of course I would allow arbitrary expressions, so you could also write ``` requires myOption in { 1, 2, 3 } ``` or ``` requires myOption in { "a", "b",...
A possible generalization could be to allow an arbitrary expression that return a Collection after the `in` keyword, so the syntax could be ``` requires myOption in newArrayList(1, 2, 3)...
If you don't care `0` would be an appropriate value?
As discussed in #236, the classes generated from the melk language are probably the wrong place for this because they might not be invoked yet when someone tries to access...
Yes thank you! Is there a way to preview the website from the PR?
Oh, so I need to install that locally first. It would be great to have a Gitpod configuration so such PRs can be easily verified in a cloud workspace. But...
What's the state of that migration? Can we start working on this?