Do not parse index sequence

[islean]

Description

We generate the index sequence from the index and index number and do not allow for any deviation from generated one. So we should not parse it from jsons since it will not impact the order either way.

Added

Changed

Fixed

How to prepare for test

• Ssh to relevant server (depending on type of change)
• Use stage: us
• Paxa the environment: paxa
• Install on stage (example for Hasta):

  bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_cg -t cg -b [THIS-BRANCH-NAME] -a

How to test

• Do ...

Expected test outcome

• Check that ...
• Take a screenshot and attach or copy/paste the output.

Review

• Tests executed by
• "Merge and deploy" approved by
  Thanks for filling in who performed the code review and the test!

This version is a

• MAJOR - when you make incompatible API changes
• MINOR - when you add functionality in a backwards compatible manner
• PATCH - when you make backwards compatible bug fixes or documentation/instructions

Implementation Plan

• Document in ...
• Deploy this branch on ...
• Inform to ...

[islean]

A bit uncertain if we should remove the validation as well? And make the index sequence a completely internal field on the FluffySample and RMLSample?

[Vince-janv]

A bit uncertain if we should remove the validation as well? And make the index sequence a completely internal field on the FluffySample and RMLSample?

I think we should remove it. It feels weird to validate something that we implicitly have already.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud