Skip to content

Remove legacy backwards-compatible data types#191

Draft
smortex wants to merge 2 commits intomasterfrom
remove-legacy-data-type
Draft

Remove legacy backwards-compatible data types#191
smortex wants to merge 2 commits intomasterfrom
remove-legacy-data-type

Conversation

@smortex
Copy link
Member

@smortex smortex commented Aug 21, 2023

When data types where added in version 5.4.0 a few years ago (#117),
backward compatibility with old catalog that used String for all
parameters was preserved.

We already did a few major releases so keeping this backward
compatibility does not make sense and we can make the types more
consistent by removing them.

@smortex smortex added this to the 8.0.0 milestone Aug 21, 2023
@smortex smortex added the backwards-incompatible This change will lead to a major version bump for the next release label Aug 21, 2023
@smortex smortex modified the milestones: 8.0.0, 9.0.0 Oct 9, 2024
@smortex smortex force-pushed the remove-legacy-data-type branch from fa9b7d6 to 698781b Compare January 4, 2026 21:03
@smortex smortex force-pushed the remove-legacy-data-type branch from 698781b to 46cb9dd Compare January 20, 2026 17:07
This fix a bunch of deprecation warnings.
When data types where added in version 5.4.0 a few years ago (#117),
backward compatibility with old catalog that used String for all
parameters was preserved.

We already did a few major releases so keeping this backward
compatibility does not make sense and we can make the types more
consistent by removing them.
@smortex smortex force-pushed the remove-legacy-data-type branch from 46cb9dd to cfa5fdf Compare January 20, 2026 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backwards-incompatible This change will lead to a major version bump for the next release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant