You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When dealing with dynamic data in e.g. LitRenderer.withProperty, it is tempting to use a java.util.Map to represent the data. This does currently not work as expected since the map instance goes down to the Introspector.getBeanInfo(type) branch which doesn't do anything meaningful for a map.
Expected behavior
Expected that myRenderer.withProperty("foo", ignore -> Map.of("foo", "bar")) would send {"foo": "bar"} as JSON to the client.
Minimal reproducible example
See above
Versions
Vaadin / Flow version: 24.6.0
The text was updated successfully, but these errors were encountered:
Description of the bug
When dealing with dynamic data in e.g.
LitRenderer.withProperty
, it is tempting to use ajava.util.Map
to represent the data. This does currently not work as expected since the map instance goes down to theIntrospector.getBeanInfo(type)
branch which doesn't do anything meaningful for a map.Expected behavior
Expected that
myRenderer.withProperty("foo", ignore -> Map.of("foo", "bar"))
would send{"foo": "bar"}
as JSON to the client.Minimal reproducible example
See above
Versions
The text was updated successfully, but these errors were encountered: