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
The initial design of the SDK used TypeScript enums for various configuration. We've removed those in favor of string unions, which fit more naturally with the way people write both TypeScript and JavaScript. However, we kept around objects that behaved like the enums for migration. Our docs haven't recommended those for a long time, and we're moving towards string values that translate directly to Wasm via jco.
We should deprecate and remove these.
The text was updated successfully, but these errors were encountered:
We decided in the team call today that we should target deprecating these for the beta, and remove them at a later stage.
The deprecation should will print a warn-level message advising users that they should consider switching to string unions soon. We will then remove them in a future update. The deprecation is tracked by #2621.
blaine-arcjet
changed the title
Deprecate and remove Enum-like objects
Remove Enum-like objects
Dec 19, 2024
From looking in to this, it seems that the objects we used to use were generated by protobuf. I'm not sure what we actually want to remove here, since they are still used for rpc.
From looking in to this, it seems that the objects we used to use were generated by protobuf. I'm not sure what we actually want to remove here, since they are still used for rpc.
The initial design of the SDK used TypeScript enums for various configuration. We've removed those in favor of string unions, which fit more naturally with the way people write both TypeScript and JavaScript. However, we kept around objects that behaved like the enums for migration. Our docs haven't recommended those for a long time, and we're moving towards string values that translate directly to Wasm via jco.
We should deprecate and remove these.
The text was updated successfully, but these errors were encountered: