Vulcan/packages/vulcan-core/lib/modules
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
..
components Improve MutatioButton 2018-07-14 09:09:01 +02:00
containers 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
callbacks.js Pass current route to router.onUpdate hook; trigger router.onUpdate from new RouterHook component; Add new event.identify hook; refactor events package, add new events-ga and events-segment packages 2017-12-17 17:42:06 +09:00
default_mutations.js merge mutation and resolver options 2018-08-10 11:50:56 +02:00
default_resolvers.js merge mutation and resolver options 2018-08-10 11:50:56 +02:00
index.js MutationButton component 2018-07-13 21:47:36 +02:00