Hello everyone, I was searching for documentation to see if there is a reason why the one to many relations is generating only a standard API entry point like entity and CRUD i.e. POST,GET,PUT,DELETE e.g.
and not something like:
SecurityUtils.isCurrentUserInRole(AuthoritiesConstants.ADMIN)doesn't work for me
eirslett front end maven plugin. I am having this error:
Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.8.0:install-node-and-npm (install node and npm) on project client-app: The plugin com.github.eirslett:frontend-maven-plugin:1.8.0 requires Maven version 3.1.0
Hello Every One,
I am new to JHipster,
I am facing many issues while create or updating entities and its relationship, Is there any way to generate CRUD from the database tables, Like we can do it in NetBeans JPA, We can Create POJO class from database tables, Then DAO and Services, Controller and Views.
is there any such way. Or suggest me to design approach we need to follow while using Jhipster.
ng g component employeesfrom the webapp/app directory? Or should I use the entity sub-generator? https://www.jhipster.tech/using-angular/
employees, then what is the best practice or tutorial to follow? My
employeespage will need Spring Boot endpoints as well as all the Angular front end components. When I think of entities, I am thinking of simple database objects. Thanks for any help.
employeespage will not be a simple crud page, where all I do is edit/update employees. It will be a complex page, where I have a table of employees, and I have an employee filter with multiple criteria. If this is a complex page, do I still create an entity for it? I am trying to leverage as much of the jhipster code generation as I can so if/when I do add a component outside of entities, I will not run into issues with routes and importing of modules.