Re-think config inclusion
Gaspard-- opened this issue · 2 comments
Gaspard-- commented
Current version doesn't seem very usable because:
- we have an order sensitive inclusion, which doesn't seem to be easy to manipulate from the API
- we have no way of "un-including" a config
The api definition of config inclusion is also broken (3 parameters, while 2 are needed)
matthiasrigaud commented
I think this issue was resolved with the last PR for the API. @Gaspard--