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
At least for parsing/deserialization this shouldn't be a problem—we can change the serialized field name to debugId and keep debug_id as a serde::alias so it can still be read. But I guess it would still count as a breaking change because serialization behavior changes.
At least for parsing/deserialization this shouldn't be a problem—we can change the serialized field name to debugId and keep debug_id as a serde::alias so it can still be read. But I guess it would still count as a breaking change because serialization behavior changes.
Fully agree. Versions are free so we should just be careful and do a major if we change it.
The relevant TC39 proposal proposes debug IDs to be in camelCase (
debugId
): https://github.com/tc39/source-map/blob/8be0fe10ad042e13f4196d17b44ddedfd6a9df58/proposals/debug-id.md?plain=1#L111We probably need to figure out some sort of migration path or cut a major for this?
The text was updated successfully, but these errors were encountered: