-
Notifications
You must be signed in to change notification settings - Fork 80
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/160 invalid date format on import csv #7525
Fix/160 invalid date format on import csv #7525
Conversation
d567e84
to
e71a2a1
Compare
app/api/csv/importEntity.ts
Outdated
/* eslint-disable no-await-in-loop */ | ||
/* eslint-disable no-unreachable-loop */ | ||
/* eslint-disable no-restricted-syntax */ |
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 really cannot put exceptions to es-lints like this. The fact that this practice has happened before should not be followed these days. So, please, remove this exceptions and lets fix the code to not have these eslint warnings:
To solve this, please create a reduce with an async callback.
Also, the no-unreachable-loop is not really solving any warning, so this was probably a previous version of the code which is no longer present, all the more reason not to include this exceptions that can later be left in the header of the file and we end up with code that is against our own guidelines.
…m:huridocs/uwazi into fix/160-invalid-date-format-on-import-csv
This reverts commit efc5f1c.
This pull request was created based on this [issue] (https://github.com/huridocs/Internal-Issues/issues/160)
Problem
We were not respecting the date format, defined at settings -> collections, to import Dates in the translated versions of the Entities.