You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For xref purposes this was the symptom reported by users, that this PR fixed:
NB this is re csv exports (JSON unaffected)
Some of the standard values in columns have changed, not the structure.
For instance:
It used to be Dref, now it is DREF
It used to be appeal, now it is Emergency Appeal
It used to be Int, now it is International Appeal
It used to be MENA, now it is Middle East North Africa
And this was the explanation given:
As part of preparatory work toward making our APIs translatable, we accidentally made a change that caused ENUM values in the database to be represented by their verbose labels and not actual values in the CSV export. This was an accidental side-effect of marking strings for translations that caused us to change the structure of how we define ENUMs that caused this bug.
This did not get caught by either our manual QA process or our API test-suite, which currently only has tests for the JSON outputs, which were unaffected by this change. We are looking into improving our testing processes to ensure we catch these changes in the future before they affect downstream data consumers.
We are extremely sorry for the breakages this has caused on your end, but are very thankful for the catch. Rest assured, we will definitely be clear with communication when we do make purposeful changes to the API that may cause breakage for our users. In this case, it was an unintentional bug, and we are very grateful to your note that has helped us track it down and fix it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Comment out Labels from EnumFields.