In the previous blog post about JHipster, you’ve already learned how JHipster works, and what are its main benefits. JHipster generates awesome codebase, but some things in the code could be improved manually. Luckily, it’s not hard to make the most out of those improvements. There are some things I wish I'd known when I started using JHipster. In this blog post, I’ll share my experience on why we use JHipster and how I’d use that knowledge to change some parts of JHipster generated code.
When you’re starting a new Spring Boot project that includes a frontend Single-page application (SPA), you might find yourself in a situation where you need to do a lot of manual work to setup the project structure. First, you define a data model, define and build a domain model, data access layer, business logic layer, service layer, and then prepare similar stuff on the frontend side. Of course, there is a Spring Initializr project that will already do a lot of stuff for you, but you can go even further and speed up your startup significantly by using a tool like JHipster.