By not going strictly with the new version, but having just some optional fields, we are able to be compatible with all version, without version specific parsing.
Later on, we can introduce a json parsing depending on the different version - maybe with this lib. But I think this complexity is not yet needed.
in ./data/app_data. The first app_data has the version 1 and the other has the verison 3. Version 2 test is not needed, as this version was never live and no order was ever created with it
And then run:
cargo run -- --retrys-for-ipfs-file-fetching=3
and you can inspect the newly created file app_data_referral_relationship for the downloaded data.
A new app_data version was introduced, in order to have the quotes stored in the order metadata.
By not going strictly with the new version, but having just some optional fields, we are able to be compatible with all version, without version specific parsing.
Later on, we can introduce a json parsing depending on the different version - maybe with this lib. But I think this complexity is not yet needed.
Testplan:
Use the following distinct_app_data.json:
in ./data/app_data. The first app_data has the version 1 and the other has the verison 3. Version 2 test is not needed, as this version was never live and no order was ever created with it
And then run:
and you can inspect the newly created file app_data_referral_relationship for the downloaded data.