-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix metadata order when downloading from data view #1748
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have agreed that branch names should only contain "-" and no "/" or "_" :) but don't change this here, just as an information for future branch names.
# Metadata related # | ||
############################################## | ||
|
||
def order_metadata(metadata: dict) -> dict: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 If you agree that this is good enough. There is still a slight difference (1. download while using the oemetabuilde 2. download while viewing the table detail page) because this only sorts the "top" level key´s. I think it's fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could adapt this also, so that key order is preserved recursively
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, that could be a quick solution. Then I would vote for implementing it : in favour of everything being as similar as possible.
Summary of the discussion
Fix inconsistent metadata structure
Type of change (CHANGELOG.md)
Changes
Workflow checklist
Automation
Closes #1696
PR-Assignee
Reviewer