On genes panel page, make more evident which genes are new after the panel is updated

[northwestwitch]

This PR adds a functionality or fixes a bug.

• Closes Entry version for genes in OMIM-AUTO panel #4956

Testing on cg-vm1 server (Clinical Genomics Stockholm)

Prepare for testing

1. Make sure the PR is pushed and available on Docker Hub
2. Fist book your testing time using the Pax software available at https://pax.scilifelab.se/. The resource you are going to call dibs on is scout-stage and the server is cg-vm1.
3. ssh <USER.NAME>@cg-vm1.scilifelab.se
4. sudo -iu hiseq.clinical
5. ssh localhost
6. (optional) Find out which scout branch is currently deployed on cg-vm1: podman ps
7. Stop the service with current deployed branch: systemctl --user stop scout.target
8. Start the scout service with the branch to test: systemctl --user start scout@<this_branch>
9. Make sure the branch is deployed: systemctl --user status scout.target
10. After testing is done, repeat procedure at https://pax.scilifelab.se/, which will release the allocated resource (scout-stage) to be used for testing by other users.

Testing on hasta server (Clinical Genomics Stockholm)

Prepare for testing

1. ssh <USER.NAME>@hasta.scilifelab.se
2. Book your testing time using the Pax software. us; paxa -u <user> -s hasta -r scout-stage. You can also use the WSGI Pax app available at https://pax.scilifelab.se/.
3. (optional) Find out which scout branch is currently deployed on cg-vm1: conda activate S_scout; pip freeze | grep scout-browser
4. Deploy the branch to test: bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_scout -t scout -b <this_branch>
5. Make sure the branch is deployed: us; scout --version
6. After testing is done, repeat the paxa procedure, which will release the allocated resource (scout-stage) to be used for testing by other users.

How to test:

1. On stage, test with the OMIM-AUTO panel version 36, where it was introduced a new gene

Expected outcome:
The functionality should be working
Take a screenshot and attach or copy/paste the output.

Review:

• code approved by
• tests executed by CR

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.78%. Comparing base (d46a7e8) to head (eddd252).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4957   +/-   ##
=======================================
  Coverage   84.78%   84.78%           
=======================================
  Files         320      320           
  Lines       19339    19339           
=======================================
  Hits        16397    16397           
  Misses       2942     2942           

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

[dnil]

⭐ Thank you, much clearer!

• The same display appears to be made in the panel_pdf_simple, perhaps patch it there as well?

There are a couple of issues with the feature overall I think, but we don't have to fix it here.

It appears a little unfortunate that we don't mark the first database_entry_version, meaning that browsing back to v1 looks odd. I suspect the design idea is that I half want to fix it, but let's save that for when someone actually wants it. I also don't really see how someone could be confused about that for very long. v1 is v1. 🤷

It would be simple to just flag genes without a database_entry_version as "new", but we also don't appear to be updating database_entry_version on regular add pending operations. 🙄

[dnil]

See also same in panel_pdf_simple! 😊

[northwestwitch]

[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