tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

Reverse argument signature of pathed query properties

Browse Source
This commit is contained in:
Aaron Carlino 2018-10-18 11:22:29 +13:00
parent 1f6a84bd8b
commit 3fcbeaddef
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/en/02_Developer_Guides/15_Customising_the_Admin_Interface/07_ReactJS_Redux_and_GraphQL.md
View File

@ -1080,7 +1080,7 @@ Now, let's update the query to fetch our new field.
*my-other-app/client/transformReadNotes.js* *my-other-app/client/transformReadNotes.js*
```js ```js
const transformReadNotes = (manager) => { const transformReadNotes = (manager) => {
manager.addField('root', 'Priority'); manager.addField('Priority');
}; };
export default transformReadNotes; export default transformReadNotes;
@ -1094,7 +1094,7 @@ In the above example, we added a single field to a query. Here's how that works:
```js ```js
manager.addField(fieldPath, fieldName) manager.addField(fieldName, fieldPath = 'root')
``` ```
The `fieldPath` argument tells the manager at what level to add the field. In this case, since the `Priority` field is going on the root query (`readNotes`), we'll use `root` as the path. But suppose we had a more complex query like this: The `fieldPath` argument tells the manager at what level to add the field. In this case, since the `Priority` field is going on the root query (`readNotes`), we'll use `root` as the path. But suppose we had a more complex query like this:
@ -1115,7 +1115,7 @@ query readMembers {
If we wanted to add a field to the nested `Company` query on `Friends`, we would use a path syntax. If we wanted to add a field to the nested `Company` query on `Friends`, we would use a path syntax.
```js ```js
manager.addField('root/Friends/Company', 'Tagline'); manager.addField('Tagline', 'root/Friends/Company');
``` ```
#### Adding field arguments #### Adding field arguments
@ -1137,7 +1137,7 @@ query ReadMembers($ImageSize: String!) {
Maybe the `Company` type has a `Logo`, and we want to apply the `ImageSize` parameter as an argument to that field. Maybe the `Company` type has a `Logo`, and we want to apply the `ImageSize` parameter as an argument to that field.
```js ```js
manager.addArg('root/Company/Logo', 'Size', 'ImageSize'); manager.addArg('Size', 'ImageSize', 'root/Company/Logo');
``` ```
Where `root/Company/Logo` is the path to the field, `Size` is the name of the argument on that field, and `ImageSize` is the name of the variable. Where `root/Company/Logo` is the path to the field, `Size` is the name of the argument on that field, and `ImageSize` is the name of the variable.
@ -1314,7 +1314,7 @@ We've extended the `onAdd` callback to take two parameters -- one for the note c
*my-other-app/client/transformCreateNote.js* *my-other-app/client/transformCreateNote.js*
```js ```js
const transformCreateNote = (manager) => { const transformCreateNote = (manager) => {
manager.addField('root', 'Priority'); manager.addField('Priority');
manager.transformApolloConfig('props', ({ mutate }) => (prevProps) => { manager.transformApolloConfig('props', ({ mutate }) => (prevProps) => {
const onAdd = (content, priority) => { const onAdd = (content, priority) => {
mutate({ mutate({