Ghost/test/utils/fixtures/csv/members-invalid-values.csv

email,name,note,subscribed_to_emails,complimentary_plan,stripe_customer_id,created_at,labels
valid2@email.com,"good name",,true,not_boolean,,2019-10-30T14:52:08.000Z,more-labels
invalid_email_value,"good name",,true,false,,2019-10-30T14:52:08.000Z,more-labels
Added validation layer to members import endpoint (#12131) no issue - Additional validation is needed for imported data because in case of bulk insertions (through knex) we bypass model layer validation - this could lead to invalid data in the database, which would be hard to fix. - Chose validation method we use for other endpoints - through JSON Schema. It proved to be very performant (200ms overhead for 50k records). When comparing it with iterative method (validating each record separately) this was adding about 17s of overhead. - Refactored returned values from "sanitizeInput" method to encapsulate more logic so that the caller doesn't have to calculate amount of invalid records and deal with error types - Whole sanitizeInput method could now be easily extracted into separate module (somewhere close to members importer) - Bumped members-csv package. It is meant to handle empty string values - '' and null, which should allow validating member records more consistently! 2020-08-17 14:28:57 +03:00			`email,name,note,subscribed_to_emails,complimentary_plan,stripe_customer_id,created_at,labels`
🐛 Fixed CSV import json-schema email validation (#12239) no-issue By using the "email" validation, we were validating emails in CSV imports using a different validator to the rest of the API. AJV's built in email validation was failing on emails with "special" characters, such as letters with an umlaut above them. This commit brings the validation for CSV imports in line with the rest of the API. 2020-09-29 14:51:35 +03:00			`valid2@email.com,"good name",,true,not_boolean,,2019-10-30T14:52:08.000Z,more-labels`
			`invalid_email_value,"good name",,true,false,,2019-10-30T14:52:08.000Z,more-labels`