Sacha Greif
26f28a98ce
Rework required field validation to make it work for intl fields when creating new documents
...
1. make intl fields use [IntlValue] and [IntlValueInput] types
2. add isIntlData marker to fields storing intl data
3. only validate intl fields that are marked as required
4. remove all instance of `__typename` from documents in edit forms
2018-08-17 19:02:44 +09:00
SachaG
861980b468
Internationalize field labels in forms and form errors
2018-07-02 16:59:29 +02:00
SachaG
35c811e791
Fix form error labels to work with intl fields
2018-06-30 11:48:37 +02:00
SachaG
e921c9762c
Remove intl fields sub-schema optional:false
2018-06-28 22:17:58 +02:00
SachaG
2d2d1033b5
Enable required locale validation for individual locales; add support for intl: true
on schema fields
2018-06-28 21:35:44 +02:00
SachaG
b066ee5b60
Bug fixes
2018-05-21 10:02:43 +09:00
SachaG
2b0f8cdd88
Change data structure of translations in db to match MongoDB standards
2018-05-21 09:42:08 +09:00
SachaG
6979ac8bee
addLocale -> registerLocale
2018-05-10 17:17:44 +09:00
SachaG
4950f10b20
Get locale from GraphQL header
2018-05-09 09:46:47 +09:00
SachaG
cf31e8f918
Use function to get IntlString type
2018-05-08 12:29:51 +09:00
SachaG
5b5884d33c
Move intl logic to vulcan:lib (keep vulcan:i18n with same API as react-i18n); add isIntlField helper; add IntlString type
2018-05-08 12:23:42 +09:00