Inaccessible bean with CollaborationBinder only triggers async errors after setTopic #72
Description
If you use CollaborationBinder with a private static bean, then there will initially not be any errors. After you add a setTopic call there will be an asynchronous exception that shows up as stacktrace in the console while the UI still renders.
To Reproduce
Can be reproduced with the example code in #71.
By adding this additional code snippet
binder.setTopic("foo", TextValueModel::new);
Expected behavior
Expected that the problem is detected as quickly as possible and reported in a way that the developer definitely notices, e.g. as an exception directly from the CollaborationBinder constructor.
Versions
- Vaadin version: 23.3.0