lumo | A high performance WebGL tile | Graphics library

It is because my next.js version is too low, ie., v11. After upgrading to the lates one, the issue is gone.

Vaadin 19 requires vaadin-button version 2.4.0. Your addon requires the same version so there is no conflict and only one version will be used.

Vaadin 20.x.x requires vaadin-button version 20.x.x. which is not compatible with your addon.

The easiest solution is to bump the version of the vaadin-button in your addon to 20:

You can use iterrows:

vaadin-input-container itself is [part="input-field"], i.e. [part="input-field"] is not child of vaadin-input-container. Thus you need to use :host as selector.

I had the same problem migrating from V21 to V22. I fixed it by deleting the target folder (and generated files in the root folder like tsconfig etc) and rebuilding again. Worked perfectly afterwards with no further problems. My suspicion was something stayed in the target folder from V21 and confused the build.

You can read the value in the onAttach method. Here is a full example class which uses a cookie for storage:

There’s no out-of-the-box support for a dark variant for Dialog specifically. You can set the whole application to use the dark theme, though.

If you only want a dark themed Dialog, you need to do what you already did, but override the background color of the element.

Vaadin works in the opposite way. If you define e.g. a view component class with @Route, then there will be a separate instance for every user when they are navigated to that view. It actually even goes further than that - if the user has the same view open in multiple browser tabs, then they will have multiple instances of that component class.

You need to make a separation between components and the data. If you put @VaadinSessionScope on a component class, then every user will have its own instance of that component. Users would be isolated from each other but it would still cause problems if the user has multiple browser tabs open. For this reason, you should almost always avoid scope annotations on component classes.

The reason multiple users see the same data is that the data is shared, regardless of the component instances. That's based on how you're configuring those components, rather than based on the life cycle of the components themselves. In the case of Grid, that's about what you're passing into the setDataProvider or setItems method. I suspect your data is either stored in a static field somewhere or in a separate Spring bean that has a wider scope (the default scope in Spring is singleton). You might want to apply @VaadinSessionScope to the bean that holds the data rather than on the component class that holds the component's own configuration.

The easies way is to use Badge add-on from the Directory. It gives you easy to use Java API for Lumo badges. You can also look via links the GitHub repo how it has been implemented.