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.
Activity
loewenheim commentedon Nov 5, 2024
At least for parsing/deserialization this shouldn't be a problem—we can change the serialized field name to
debugIdand keepdebug_idas aserde::aliasso it can still be read. But I guess it would still count as a breaking change because serialization behavior changes.lforst commentedon Nov 5, 2024
Fully agree. Versions are free so we should just be careful and do a major if we change it.
debugIdinstead ofdebug_idsentry-cli#2221feat(debugId): Serialize source maps with `debugId`, not `debug_id` (g…