Leif Åstrand

Automatic handling of single-property objects might make sense but I suspect we would still also need to support `@JsonCreator` and `@JsonValue` to allow customization.

The issue might actually be on the Flow side since it seems like the route registry is empty after the redeploy. The problem isn't only that view missing from the...

We should keep in mind that API versioning as a general concept is also used for cases with an API is exposed for use by 3rd party clients or native...

TypeScript doesn't help for the situation when the application is redeployed so that the server has a new version of the endpoints while the user still has an old version...

Deprecation is a development-time strategy whereas the main problem in our case is a mismatch between different parts of the application while it's running. Deprecation helps the developer keep the...

What makes you need that level of control? I'm asking because we know we need to add something, but we haven't yet understood the requirements well enough to be certain...

I agree. It's better to avoid injecting any property in the cases that are not explicitly supported since it's more convenient for the developer to include an additional property than...

Note that it's not enough to give a different configuration for the grid since `` expects the grid and the form to have data in the same format so that...

In addition to `executeJs`, there seems to be at least two other parts in the framework that could cause challenges with typical CSP settings for JavaScript: * [`lit-renderer.ts`](https://github.com/vaadin/flow-components/blob/main/vaadin-renderer-flow-parent/vaadin-renderer-flow/src/main/resources/META-INF/resources/frontend/lit-renderer.ts) creates a...

You can implement you custom callback to throw an exception instead of falling through to the default implementation that uses `eval`. I'm not aware of any current approach that would...