Switch to using camelCase for metadata fields #2507
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #2438
preview URL: https://switch-to-camelcase.loculus.org/
Summary
After a long discussion today we have decided to switch all metadata fields to camelCase to ensure consistency in fields for users.
Screenshot
PR Checklist
I see the error
No data found in /data/ for ingestion
which is odd I thought we fixed this on LAPIS => caused by the fact that pango_lineage is a metadata type in LAPIS and pangoLineage is not, I have now fixed thisFuture work