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
{{ message }}
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.
Convenient sometimes, but then surprisingly things don't work, when updates come from outside that page's thread (either server push, or by a user interaction on another page).
More importantly, a lot of methods in reactive call methods that take an implicit Page but don't themselves take one. By (at least temporarily) deprecating currentPage, the compiler will reveal the trail.
Perhaps currentPage doesn't need to be removed, and we can just leave the @deprecated annotation in order to generate compiler warning messages.
Does anyone think that this should bump the version number?
The text was updated successfully, but these errors were encountered:
Convenient sometimes, but then surprisingly things don't work, when updates come from outside that page's thread (either server push, or by a user interaction on another page).
More importantly, a lot of methods in reactive call methods that take an implicit Page but don't themselves take one. By (at least temporarily) deprecating currentPage, the compiler will reveal the trail.
Perhaps currentPage doesn't need to be removed, and we can just leave the @deprecated annotation in order to generate compiler warning messages.
Does anyone think that this should bump the version number?
The text was updated successfully, but these errors were encountered: