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 Dec 28, 2022. It is now read-only.
I think we need a "preupgrade" hook that, if set, runs when the user calls update, allowing them to ensure certain conditions around the upgrade. this would just be a view, like non-sparse mode (infact non-sparse could be implemented as a hook).
For example:
consts=core.session({preupgrade(latest){// where latest is a session that is on the latest lengthawaitlatest.get(latest.length-1)// always ensure the latest block is therereturnlatest.length// can optionally return the length we're upgraded to }})// calls aboveawaits.update()
We might wanna allow simple naming of the hooks also so users can define a couple, but let's defer that to after we have one working. The pointer a preupgrade session is on should also be stored in the oplog, so we can checkout the current existing one on restart
The text was updated successfully, but these errors were encountered:
I think we need a "preupgrade" hook that, if set, runs when the user calls update, allowing them to ensure certain conditions around the upgrade. this would just be a view, like non-sparse mode (infact non-sparse could be implemented as a hook).
For example:
We might wanna allow simple naming of the hooks also so users can define a couple, but let's defer that to after we have one working. The pointer a preupgrade session is on should also be stored in the oplog, so we can checkout the current existing one on restart
The text was updated successfully, but these errors were encountered: