resources[resource.name].api = $resource(operations[relativePath].url + '/:id', { id: '@id' });
var entities = resources[resource.name].api.query();
scope.entities = entities;
resources[resource.name].entitites = entities;
ng-repeat='entity in resource.entities'
ng-repeat='entity in entities'
resource
is already on the scope.
Actually MBEFE is exactly a generator for a standardized CRUD UI. It just doesn't work with swagger right now.
MBEFE is just an early version of a tree component, it doesn't have to end up working the way it does now.
What I am thinking is that swagger is a part of the solution. If it is like JSON-schema, it can be extended.
Aha, I see. Personally, I always just put those little buggers in a generalized tree. That is why I started with a tree.
I realized that customers actually like working with entities in trees.
Anyway, to one could do, then, is to create a forth declarative syntax that works on the application-level.
So one ends up with:
With regards to number four, I am not sure that it is needed, because Isn't that basically the swagger framework and Angular in unison?
Shouldn't swagger be an angular framework that doesn't have a form standard, but which, with minimal input, can generate a UI but have several ways to be controlled?