ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #jhipster
JHipster generates entity forms that utilize server-side validation to display error messages upon form submission. While the UI visually highlights fields with error classes, the generated HTML templates do not include aria-live regions or role="alert" for these message containers. As a result, screen reader users may not be notified that validation errors
When generating a repeatable development environment, JHipster creates a docker‑compose.yml that uses the latest tag for the application, database, and monitoring containers. This configuration depends on Docker Hub's mutable latest tag, which can change between pulls and lead to inconsistent images across machines or CI runs. The goal is to guarantee that t
Configuration Goal JHipster generates Spring Boot applications using HikariCP as the default connection pool implementation. The generator's application.yml template includes hikari configuration, but the exact logic for calculating maximumPoolSize may not be fully transparent to developers deploying to production environments. Relevant Constraints The defau
Angular Proxy vs Spring Boot CORS In JHipster‑generated projects the Angular proxy (proxy.conf.json) forwards API calls to the Spring Boot backend during development. The backend typically registers a CORS filter that controls cross‑origin request handling. When both the proxy and filter are active, the forwarding of cookies and authorization headers is unce
JHipster generates Spring Data JPA repositories that extend JpaRepository and expose server-side pagination via Pageable and Page. The frontend requests pages using page and size query parameters, and Hibernate translates the abstractions to database-specific LIMIT and OFFSET. The design goal is to understand the conditions under which paginated entity retri
Establishing a repeatable local development environment for JHipster-generated applications requires a stable Docker Compose baseline across teams. The documented configuration transition with the Spring Boot 3 and Java 17 baseline in JHipster 8+ changed service profiles, healthcheck expectations and environment variable conventions compared with JHipster 7
JHipster Helm Chart Configuration for Pre‑Run Liquibase Migration Job The goal is to guarantee that database schema updates are applied exactly once and before any new version of the application starts, while preserving the ability to run destructive change‑sets safely in a Kubernetes RollingUpdate. Currently the generated Helm chart relies on pod‑startup Li
JHipster scaffolds Spring Data JPA repositories and REST resources that expose list endpoints with Spring Data Pageable. The generated methods accept page, size and sort query parameters and return org.springframework.data.domain.Page, which is translated by JPA/Hibernate to LIMIT/OFFSET SQL. The goal is to bound queries over a large dataset and keep paginat
Context JHipster’s entity sub‑generator creates a @KafkaListener that relies on Spring Kafka’s default error handling. When the listener throws an exception after a database write, the consumer may either skip the record, retry it, or commit the offset prematurely, leading to duplicate writes. Unresolved Decision The generated code does not include a dead‑le
bootstrap
hibernate
helm
kubernetes