feat: use Ciqual table 2025 version in addition to 2020 - #14306
feat: use Ciqual table 2025 version in addition to 2020#14306stephanegigandet wants to merge 18 commits into
Conversation
…dfacts-server into ciqual-ingredients
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #14306 +/- ##
==========================================
+ Coverage 50.31% 54.40% +4.09%
==========================================
Files 103 104 +1
Lines 26400 26475 +75
Branches 6316 6330 +14
==========================================
+ Hits 13282 14403 +1121
+ Misses 11357 10128 -1229
- Partials 1761 1944 +183
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
/update_tests_results |
|
There was a problem hiding this comment.
Do we need to keep both the source .xls and derived .csv’s around? If so, maybe we could store the .xls files in git-lfs storage rather than directly in the git repository itself? (The repository is already rather big even without adding (more) MB-size binary blobs to it…)



We currently use the 2020 Ciqual table in Product Opener. There is an updated 2025 table.
This PR adds the 2025 table, and we still use the 2020 table as fallback. This is because some Ciqual codes from 2020 do not exist in the Ciqual table 2025.
Total entries in 2020: 3185
Total entries in 2025: 3484
Only in 2020: 182
Only in 2025: 481
In both versions: 3003