Should generate code for:
pages for create, delete, update, list objects or view data for some row
This should be generic mechanism which will be used for create pages for update metamodels and for update specific cusom classmetamodels adres by user.
This should be generated based on classmeta modela, fields, validators.
Generated code should be based on jhipster
modules loaded lazily or not lazily (configurated)
Every endpoint family will be separated module.
form reactive or template (configured) in first release reactive forms should be
custom template for components (add, edit, view, table/list with search), every component and service for it can have own template when not provided then default one will be used.
every input (field) can have own template.
adding something to list via modal or nested list on form? (configurated), maybe something will be from other service could used via other endpoint or created directly via endpoint (composition or relation).
custom validation could be written in separated files or as code which will be placed to components.
during adding template for fields should be opportunity for show what should be imported/declared to component.
child routes, not in one file with routes, modules should attach their routes
Should generate code for: pages for create, delete, update, list objects or view data for some row
This should be generic mechanism which will be used for create pages for update metamodels and for update specific cusom classmetamodels adres by user.
This should be generated based on classmeta modela, fields, validators.
Generated code should be based on jhipster
modules loaded lazily or not lazily (configurated) Every endpoint family will be separated module. form reactive or template (configured) in first release reactive forms should be custom template for components (add, edit, view, table/list with search), every component and service for it can have own template when not provided then default one will be used. every input (field) can have own template. adding something to list via modal or nested list on form? (configurated), maybe something will be from other service could used via other endpoint or created directly via endpoint (composition or relation). custom validation could be written in separated files or as code which will be placed to components. during adding template for fields should be opportunity for show what should be imported/declared to component.
child routes, not in one file with routes, modules should attach their routes