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
While working on the refactoring in #471, I improved some APIs in the runtime package, but to keep the changes easier to review (and to minimize impact on existing users), I kept most of the API additions hidden in the docs and left the existing types and functions in place.
I'm filing this separate issue that will un-hide those new APIs and mark the existing ones as deprecated. The deprecated ones will be removed in a future release, but this approach will give users time to update to the new code.
Most of these changes are below the radar and not typically used directly by users, so there should be limited impact anyway. The changes mostly impact the template code.
The text was updated successfully, but these errors were encountered:
Remove WasmBuffer from public API (it is now an implementation detail and isn't something that users would work directly with anyway, so no need to deprecate)
Add (unhide) initWasmModel
Deprecate initWasmModelAndBuffers (use initWasmModel instead; the worker code in runtime-async has already been updated to deal with either return type)
I am in the middle of merging a few large branches to main (for issues #471, #437, #479) so that they can be tested together as a whole before npm publishing them. I decided while working on these issues that it is easier to remove (rather than deprecate) those APIs since they are below the radar for most users, and it's not worth trying to maintain the old versions any longer. The proposed list from above has been implemented already (as removals rather than deprecations), see #437 and #479 for more details on the latests API changes.
While working on the refactoring in #471, I improved some APIs in the runtime package, but to keep the changes easier to review (and to minimize impact on existing users), I kept most of the API additions hidden in the docs and left the existing types and functions in place.
I'm filing this separate issue that will un-hide those new APIs and mark the existing ones as deprecated. The deprecated ones will be removed in a future release, but this approach will give users time to update to the new code.
Most of these changes are below the radar and not typically used directly by users, so there should be limited impact anyway. The changes mostly impact the template code.
The text was updated successfully, but these errors were encountered: