SachaG
d5cad5288a
Document is not defined in create mutation
2018-10-10 17:40:16 +09:00
SachaG
335cda6cf0
Improve thrown errors
2018-10-10 17:35:01 +09:00
SachaG
5fc0e30f40
Fix ESLint
2018-09-12 11:59:00 +09:00
ochicf
eb544faa07
register callbacks only for the created mutations
2018-08-10 11:51:43 +02:00
ochicf
b31ff85b8c
merge mutation and resolver options
...
This makes possible to only specify a subset of options.
As an example, imagine we want to pass a customized `updateCheck` function to `getDefaultMutations`. Before this commit options weren't merged, so all of them had to be specified:
```
getDefaultMutations({
typeName,
collectionName,
options: {
create: true,
update: true,
upsert: true,
delete: true,
updateCheck: () => true,
});
```
After the commit:
```
getDefaultMutations({
typeName,
collectionName,
options: {
updateCheck: () => true,
});
```
2018-08-10 11:50:56 +02:00
ochicf
9e9d818678
collectionName can now be specified as an argument
2018-08-10 11:24:38 +02:00
SachaG
910c932f61
Get rid of single argument level of indirection in mutations; add additional checks to avoid empty selectors
2018-08-07 16:20:24 +09:00
SachaG
d9bc8b8c88
New default mutations/default resolvers API
2018-06-17 07:49:33 +09:00
SachaG
51acfa7ffc
Migrate new callbacks to new single argument API
2018-06-15 10:18:20 +09:00
SachaG
905bacbe88
Update permissions
2018-06-14 17:45:02 +09:00
SachaG
60f47a5189
Various small fixes (thanks @justinr1234)
2018-06-08 13:31:15 +09:00
SachaG
2318a95d66
Make mutations backwards compatible
2018-06-06 09:32:30 +09:00
SachaG
f1652ae025
arguments -> args
2018-06-06 09:07:13 +09:00
SachaG
c8b57ab60e
Fix withMulti
2018-06-06 07:36:25 +09:00
SachaG
b92944b6cc
Working on default mutations and mutators
2018-06-05 16:39:03 +09:00
SachaG
1d3921287c
Refactored GraphQL schema generation code to use new GraphQL templates
2018-06-05 10:04:20 +09:00
SachaG
f3ba2cc59f
Working on GraphQL template system for GraphQL schema generation
2018-06-04 11:22:49 +09:00
SachaG
96eab44309
Start CRUD renaming
2018-06-02 18:49:53 +09:00
Eric Burel
bf9ebaf57c
Allow guests to create document as a default
...
Hi, using when using the default mutations, you can't allow a guest user to create a document, even if you allowed it for `guests` when setting up permissions. This is because a undefined `user` will always trigger a `false` during the "new" check.
I think it is safe to remove this, because anyway you have to manually tell who can create document (or so I think, maybe I'm wrong?) so you can't allow guests to create documents by mistake.
2018-03-03 23:11:33 +01:00
SachaG
861e65e641
Refactor connectors code to avoid repeating getSetting
2018-03-03 11:39:56 +09:00
SachaG
270c6b4215
Use connectors and await/async
2018-02-18 15:26:59 +09:00
SachaG
a899532c4f
mutation -> mutator
2018-02-17 11:17:25 +09:00
Justin Reynolds
9212a1970e
Add upsert mutation
2018-01-28 22:26:05 -06:00
SachaG
05084e6fb5
Add support for GraphQL comments/descriptions for fields, queries, mutations, types
2018-01-02 13:04:33 +09:00
SachaG
010fff2e21
Implement server-side internal event tracking
2017-12-18 09:57:17 +09:00
Sacha Greif
7accd7c6ae
improve calback documentation; fix edit validation issue; add postedAt callback
2017-11-08 10:06:01 +09:00
Sacha Greif
50943f01de
First pass at /callbacks dashboard
2017-10-21 15:58:02 +09:00
SachaG
bac853d438
fix default mutation bug
2017-08-24 13:16:33 +09:00
SachaG
e4e1f0c41c
default mutations can now take options object; add Flash core component; fix Stripe bug
2017-08-07 16:02:29 +09:00
ochicf
6f61f74a34
Fix remove permission strings
...
Transform collection name to lower case as it is done with the other permission strings.
2017-07-19 18:49:11 +02:00
SachaG
7ff1ada7d9
add new default resolvers and default mutations; improve the way field resolvers are defined
2017-07-03 10:54:10 +09:00
