plata
plata
During the load. It would replace the repository DTO hierarchy.
> otherwise it is not clear to which application a script belongs and to which category an application belongs It is because the includes are structured like `applications.games.xyz`, `applications.development.xyz` etc....
We need the namespace hierarchy only for scripts which are listed from Java. For stuff like utils, it's completely irrelevant where they are located in the hierarchy and they do...
Yes, that's what I had in mind. The thing I'm not quite sure about: Should the `RepositoryFetcher` know about `EngineDTO` etc. directly or should it only know generic scripts? In...
Yes. However, that's only a small point. First, we should decide if we want continue with the hierarchy or not. In my opinion, we should remove it because it enforces...
Makes sense. However, I do not find the time currently to do something about it.
I don't think this is feasible. In general, we cannot ensure that the required dependencies to build or even run an application are available.
And who should provide that container?
The general idea was that verbs are first class citizens like any other app/plugin etc. Therefore it would be difficult (conceptionally) to add a different json for verbs. Is there...
Then I would suggest simply a "description" field in script.json.