hilla
hilla copied to clipboard
vaadin
Build better business applications, faster. No more juggling REST endpoints or deciphering GraphQL queries. Hilla seamlessly connects Spring Boot and React to accelerate application development.
When a developer specifies a property (path) that does not exist, for example in an auto grid's `visibleColumns` or in an auto form's `fieldOptions`, then it is just silently ignored....
According to #1751 and #1759, the repository configuration lacks a configuration that forbids unintentional test skipping in PRs. To address it, I would suggest addressing it in four different ways:...
Auto form should inline fields from nested entities referenced with `@OneToOne`
For many-to-one properties auto form should add a single-selection field. A `ComboBox` seems like the most useful default field to use as it supports lazy-loading. The field should render a...
If the entity the form is editing has a `@Version` field and submit/save fails because of using an old entity, there should be an error message stating the issue ("somebody...
### Describe your motivation When dealing with DTOs instead of entities, it is easier to project data with a DTO class different that the one used for Update and Save...
### Describe your motivation There are cases, like working offline, where it would be useful to be able to get the automatic generation provided by AutoGrid/Form/Crud, but work with a...
### Describe the bug If a Hilla endpoint is passing or returning an object with a public getter/setter that starts with a digit, Hilla auto-generates TS types that start with...
### Describe the bug Trying to filter a BigDecimal field results in an exception. ### Expected-behavior It works. ### Reproduction Filter a column containing BigDecimal values. ### System Info Hilla...
### Describe the bug The generator for `@JsonSubTypes` assumes that there will always be a property named `@type`. This is the case with the `@JsonTypeInfo(use = JsonTypeInfo.Id.NAME, include = JsonTypeInfo.As.PROPERTY)`...
