Closed rosibaj closed 3 years ago
A dictionary change is rejected as a breaking change if a a field type is changed from integer to number
integer
number
Example: Migrate: to dictionary version 80.5 in the ARGO QA Environment:
{ "_id": "604bf2c33811dc001ea01bb1", "name": "ICGC-ARGO Data Dictionary", "version": "80.5" },
There is a migration manager in the code that handles these rules that can be edited.
migration manager
This should be allowed as all numbers are integers, thus no data would be broke. It is making a field more permissive, not less permissive.
tested with several dictionary migrations in the sprint including int --> number
deployed to staging
Confirmed on Ulyssus Release May 10, 2021
Detailed Description
A dictionary change is rejected as a breaking change if a a field type is changed from
integer
tonumber
Example: Migrate: to dictionary version 80.5 in the ARGO QA Environment:
There is a
migration manager
in the code that handles these rules that can be edited.Expected Behaviour
This should be allowed as all numbers are integers, thus no data would be broke. It is making a field more permissive, not less permissive.