Feature Model Anomaly + Subroutine Framework

[Elscrux]

No description provided.

[Elscrux]

@schweikart Thank you for the review, I've pushed a lot of tweaks

[Elscrux]

Everything should be ready now @schweikart :)

[Elscrux]

Oh, that's probably my bad.

SolverSelection would be more common as you can use these components just like any other:

<SolverSelection/> instead of getSolvers() (line 66)

One more thing:
This actually seems to cause problems! It resets the selection every time I try to select an option. Do you know what could cause this?

[Elscrux]

export type SolveMap = {
[key: string]: SolveRequest
}
maybe use a Map instead? This typing will set all attributes of SolveMap instances to be SolveRequests but toString and other built-in attributes / functions are not SolveMaps!

I had a problem with Map<K,V> in the past, so I used this, but I can't replicate it now, so I'll use that instead.

I actually replicate the issue now. As Map<K, V> is an object, it gets formatted differently in the JSON that is sent to the backend.
The backend can't properly parse this format to a Java Map.

[schweikart]

Nice work!