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
If you try to use Collaboration Engine without enabling @Push in Flow, then things will typically be broken in ways that are not obvious. This is a quite common mistake to do when trying out something simple and it can be quite difficult to debug.
There is already logic in ComponentConnectionContext::checkForPush that checks for this and logs a warning (in development mode), but this warning is easily ignored. In addition to logging a warning, the same logic could also enable push if it isn't enabled.
We should then also provide a way of configuring CE to not enable push in case the developer for some reason wants to e.g. use UI::setPollInterval instead. API for this could be in CollaborationEngineConfiguration, e.g. as configuration.setAutomaticallyActivatePush(false).
The text was updated successfully, but these errors were encountered:
If you try to use Collaboration Engine without enabling
@Push
in Flow, then things will typically be broken in ways that are not obvious. This is a quite common mistake to do when trying out something simple and it can be quite difficult to debug.There is already logic in
ComponentConnectionContext::checkForPush
that checks for this and logs a warning (in development mode), but this warning is easily ignored. In addition to logging a warning, the same logic could also enable push if it isn't enabled.We should then also provide a way of configuring CE to not enable push in case the developer for some reason wants to e.g. use
UI::setPollInterval
instead. API for this could be inCollaborationEngineConfiguration
, e.g. asconfiguration.setAutomaticallyActivatePush(false)
.The text was updated successfully, but these errors were encountered: