Save Ensembl transcript ID and exon number in exons table

[northwestwitch]

Description

Added/Changed/Fixed

• Closes Save transcript_id info and exon number in exons database documents #370

exons table before:

exons table after:

How to test

• Locally, drop and re-create the sql database
• Load genes, transcripts and exons
• Check the exons table

Expected outcome

• It should contain the ensembl_transcript_id field

Review

• Tests executed by CR
• "Merge and deploy" approved by

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

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.15%. Comparing base (719f1b8) to head (4d2242f).
Report is 101 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #371      +/-   ##
==========================================
+ Coverage   90.18%   93.15%   +2.96%     
==========================================
  Files          30       31       +1     
  Lines        1457     1504      +47     
==========================================
+ Hits         1314     1401      +87     
+ Misses        143      103      -40     

Flag	Coverage Δ
unittests	93.15% <100.00%> (+2.96%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[northwestwitch]

Since I'm touching the code I think I'll also add the exon number in transcript to the table

[northwestwitch]

Tested locally and it works, see screesnhot in comment above

[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 SonarCloud

[northwestwitch]

Pydantic model already contained this field, so I think I I meant to include it at some point, but forgot to update the SQLAlchemy exon model