Miki
Given the amount of dependencies and features, `ObjectFieldFactory` should probably be a separate library. This should be implemented at the same time as #366 and #385.
@vaadin-miki is not a person that is familiar with JS practices. The code can definitely be improved in terms of readability, best practices, patterns, etc. Please help this project by...
Investigate if the hack around the lack of run-time themes (https://lumme.dev/2021/06/15/dynamic-theming-in-vaadin-flow.html) is something that can be turned into a component with events. If so, check if Carbon theme (https://github.com/anezthes/carbon-vaadin14) can...
Those components that have client-side counterparts basically just store JS functions. Consider replacing polymer templates with something more efficient, like lit. Or even plain JS.
Text selection setup takes place `onAttach`, however in case of `GridPro` the component is not fully available and thus cannot be properly configured. More specifically, in `text-selection-mixin.js`, inside `listenToEvents()`, `webComponent.inputElement`...
#170 allows querying the user before leaving the page, but there is currently no way to find out whether or not the user stayed on the page (because `unload` events...
Check if this is doable at all. Idea for a new component - `SuperTimePicker` that allows custom formatting for `TimePicker` on the frontend. The same code should be reused in...
As a neat feature it could be allowed for text fields and text areas to grow while the input is being typed. This can be done by listening to change...
Add more translations to `superdatepickeri18n.properties`. The list below is by no means complete: - [ ] Chinese - [ ] Estonian - [ ] French - [x] German - [x]...
Currently `ItemGrid` only accepts items through `setItems`. Check if it is worth the effort to integrate it with Vaadin data model and data providers.