fix: deprecate inconsistent config param case (#4172)

This commit is contained in:
andreascm
2020-08-31 19:25:48 +08:00
committed by GitHub
parent f1376aa5c3
commit 88a5a8098e
31 changed files with 409 additions and 144 deletions

View File

@ -34,8 +34,8 @@ collections: # A list of collections the CMS should be able to edit
label: 'Publish Date',
name: 'date',
widget: 'datetime',
dateFormat: 'YYYY-MM-DD',
timeFormat: 'HH:mm',
date_format: 'YYYY-MM-DD',
time_format: 'HH:mm',
format: 'YYYY-MM-DD HH:mm',
}
- label: 'Cover Image'
@ -108,9 +108,9 @@ collections: # A list of collections the CMS should be able to edit
name: 'post'
widget: 'relationKitchenSinkPost'
collection: 'posts'
displayFields: ['title', 'date']
searchFields: ['title', 'body']
valueField: 'title'
display_fields: ['title', 'date']
search_fields: ['title', 'body']
value_field: 'title'
- { label: 'Title', name: 'title', widget: 'string' }
- { label: 'Boolean', name: 'boolean', widget: 'boolean', default: true }
- { label: 'Map', name: 'map', widget: 'map' }
@ -139,8 +139,8 @@ collections: # A list of collections the CMS should be able to edit
name: 'post'
widget: 'relationKitchenSinkPost'
collection: 'posts'
searchFields: ['title', 'body']
valueField: 'title'
search_fields: ['title', 'body']
value_field: 'title'
- { label: 'String', name: 'string', widget: 'string' }
- { label: 'Boolean', name: 'boolean', widget: 'boolean', default: false }
- { label: 'Text', name: 'text', widget: 'text' }
@ -187,8 +187,8 @@ collections: # A list of collections the CMS should be able to edit
name: 'post'
widget: 'relationKitchenSinkPost'
collection: 'posts'
searchFields: ['title', 'body']
valueField: 'title'
search_fields: ['title', 'body']
value_field: 'title'
- { label: 'String', name: 'string', widget: 'string' }
- { label: 'Boolean', name: 'boolean', widget: 'boolean' }
- { label: 'Text', name: 'text', widget: 'text' }

View File

@ -172,9 +172,9 @@
render: function() {
// When a post is selected from the relation field, all of it's data
// will be available in the field's metadata nested under the collection
// name, and then further nested under the value specified in `valueField`.
// name, and then further nested under the value specified in `value_field`.
// In this case, the post would be nested under "posts" and then under
// the title of the selected post, since our `valueField` in the config
// the title of the selected post, since our `value_field` in the config
// is "title".
const { value, fieldsMetaData } = this.props;
const post = fieldsMetaData && fieldsMetaData.getIn(['posts', value]);