This website requires JavaScript.
Explore
Help
Sign In
darkhelm
/
notifications-api
Watch
1
Star
0
Fork
0
You've already forked notifications-api
mirror of
https://github.com/GSA/notifications-api.git
synced
2025-12-22 16:31:15 -05:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
Files
10ea8c38cda4cea8deb8979c40f2802726b734e4
notifications-api
/
test_csv_files
/
sms.csv
3 lines
53 B
CSV
Raw
Normal View
History
Unescape
Escape
Process CSV files with column headers of any case Implements and depends on: https://github.com/alphagov/notifications-utils/pull/27 Should be merged and deployed before the same change in the admin app.
2016-04-29 17:24:00 +01:00
PHONE NUMBER
,
IGNORE THIS COLUMN
Accept CSV files with additional columns Currently when the Celery task processes a CSV it will call the API with the values for all the non-recipient columns in the `personalisation` field. This means that those API calls would fail, even though the CSV has been processed ‘successfully’. This was not being caught by the tests, so this commit adds extra tests to check what data the task is passing to the API call. It then updates utils to version 2.0.1 which brings in this fix: https://github.com/alphagov/notifications-utils/pull/10
2016-03-09 07:27:26 +00:00
+441234123123
,
nope
Reference in New Issue
Copy Permalink