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
b55096855e
added TODOs
2018-08-10 11:24:50 +02:00
ochicf
9e9d818678
collectionName can now be specified as an argument
2018-08-10 11:24:38 +02:00
SachaG
9d53c33727
Fix queryOne query variables
2018-08-10 13:08:49 +09:00
SachaG
497987d91e
Export account helpers
2018-08-10 13:08:12 +09:00
SachaG
a1a3ffbb8c
Merge branch 'revert-single-arguments' into devel
2018-08-10 11:16:40 +09:00
SachaG
87ed3ea5ea
Use UNSAFE_componentWillReceiveProps to compare old props and new props before resetting state when props change
2018-08-09 11:41:06 +09:00
SachaG
fe86f84870
Put currentDocument on state, too; use isEmptyValue to test for empty values (will catch [], '', and undefined as well as null)
2018-08-07 16:42:45 +09:00
SachaG
2071307662
Merge branch 'devel' into revert-single-arguments
2018-08-07 16:20:29 +09: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
92a8ae8e75
Improve error handling in nested arrays and nested objects
2018-08-07 16:05:24 +09:00
SachaG
9569200b95
Improve error handling by parsing GraphQL error messages
2018-08-07 15:43:03 +09:00
SachaG
d9784ad0aa
Improve StaticText form component with basic URL parsing
2018-08-07 15:37:51 +09:00
SachaG
ae12907877
Merge branch 'devel' into feature/nested-schema
2018-08-07 10:16:40 +09:00
SachaG
8347dffb2e
Fix user creation onCreate/onInsert step
2018-08-07 10:13:59 +09:00
SachaG
2f4a0acb8e
Get rid of merging to generate document; instead update currentDocument every time updateCurrentValues is called. Add support for { mode: 'merge'} in updateCurrentValues options.
2018-08-07 10:13:06 +09:00
SachaG
929e479f59
Do not pass down nestedInput prop in intlInput components to avoid treating them like Nested Objects components
2018-08-06 10:52:37 +09:00
SachaG
059d2651b9
Merge branch 'devel' into lbke-feature/nested-schema
...
# Conflicts:
# packages/vulcan-forms/lib/components/Form.jsx
# packages/vulcan-forms/lib/components/FormComponent.jsx
2018-08-06 10:46:40 +09:00
SachaG
a9d81cb747
Simplify getValue; do not merge in getValue anymore, instead get value from Form's getDocument()
2018-08-06 10:43:00 +09:00
SachaG
cdd59a1cbf
When checking to update FormComponent when a field has been deleted, update parent component if child has been deleted.
2018-08-06 10:31:06 +09:00
SachaG
e27f5af9e1
Make Checkboxgroup and Select handle their own value formatting
2018-08-06 10:30:15 +09:00
SachaG
e1faef0d39
Add getFieldType, getNullValue form utils
2018-08-06 10:29:36 +09:00
SachaG
517fc97ade
Change getDocument's merge function to allow array replacement (e.g. replace ['foo', 'bar', 'baz'] by ['foo', 'baz'] if 'bar' has been deleted) instead of always attempting to merge
2018-08-06 10:29:06 +09:00
SachaG
d94a024973
Refactor Checkboxgroup to full function syntax
2018-08-05 21:16:38 +09:00
SachaG
9b4d913fab
Handle form deletions more explicitly (split into two cases); pass value down to FormNested; uniq -> uniqBy
2018-08-05 11:17:46 +09:00
SachaG
d50a4cb5f9
Use named function for better debugging
2018-08-05 10:57:43 +09:00
SachaG
eb9a86ee47
uniq -> uniqBy
2018-08-05 10:30:56 +09:00
SachaG
96a396fd8c
Merge branch 'feature/nested-schema' of https://github.com/lbke/Vulcan into lbke-feature/nested-schema
2018-08-03 11:44:20 +09:00
SachaG
45afb1d1f7
Don't use arrow function since it breaks arguments
2018-08-03 11:44:00 +09:00
SachaG
4ecac53112
Fix #2027
2018-08-03 11:14:15 +09:00
SachaG
6045777ff7
Small modal refactor; footerContent -> footer
2018-07-30 14:59:36 +09:00
SachaG
8613f8b79f
Upgrade product creation for new Stripe API
2018-07-30 14:59:10 +09:00
SachaG
dd8b1a9857
Merge branch 'devel' of https://github.com/VulcanJS/Vulcan into devel
2018-07-28 12:42:43 +09:00
Sacha Greif
e8d9f06af3
Merge pull request #2025 from OrigenStudio/feature/dynamic-fragment-initalization
...
Dynamic fragment initalization
2018-07-28 12:38:34 +09:00
Sacha Greif
287be4371c
Merge pull request #2024 from OrigenStudio/fix/open-crud-forms
...
Pass opencrud field properties to the form
2018-07-28 12:37:48 +09:00
Eric Burel
e79b8a524f
updated schema_utils and FormComponent to correctly detect nested objects
2018-07-27 17:27:44 +02:00
ochicf
65cc9e0b38
initialize fragment when trying to retrieve it for the first time
2018-07-27 10:17:53 +02:00
ochicf
e2fe2ce556
initalizeFragments can now be parametrized with fragments to initialize
2018-07-27 10:16:56 +02:00
ochicf
d661e1a48b
add opencrud field properties so they are passed to the form
2018-07-27 09:50:44 +02:00
Eric Burel
b5e54ead17
Splitted FormNested between objects an arrays
...
Nested form is much simpler for objects than for arrays.
2018-07-26 17:25:33 +02:00
Eric Burel
25db5c04b8
load Components correctly in tests
...
Now `vulcan:ui-bootstrap` is explicitely loaded in the `vulcan:forms`
package. This avoid undefined `Components.Button` if the use did not
load a specific styling package
2018-07-26 16:39:40 +02:00
Eric Burel
d21dd5fcfa
wrote passing tests and a failing test for nested objects
2018-07-25 18:03:43 +02:00
Sacha Greif
c68604876b
Merge pull request #2022 from lbke/bugfix/nested-objects-b34f0a25ce0c775a29a14241b14e9bc0e47976c8
...
Bugfix/nested objects b34f0a25ce
2018-07-25 05:12:21 +02:00
Eric Burel
56eb3ab4b6
fixed nested form generation
...
Schema must be passed explicitely to the field retrieval methods
(otherwise the main schema will be used instead of the nested schemas)
2018-07-24 20:33:43 +02:00
Eric Burel
4d6e87cbca
pass the nested schema to the field retrieval methods
2018-07-24 18:29:27 +02:00
Eric Burel
474456148e
setup tests
2018-07-24 18:13:34 +02:00
Eric Burel
b2c5f8c352
Fixed backers image link
2018-07-24 18:07:52 +02:00
Eric Burel
9e2233f0c9
Merge remote-tracking branch 'upstream/devel' into devel
2018-07-24 15:50:54 +02:00
Sacha Greif
858fbece5e
Merge pull request #2021 from Apollinaire/getParametersFix
...
collection.getParameters handles schema extension for searchable fields
2018-07-23 15:14:44 +02:00
Apollinaire
fefc21bb2f
collection.getParameters handles schema extension for searchable fields
...
Instead of using `schema` passed when creating the collection, `getParameters` should fetch the schema from `collection.simpleSchema()._schema` to include the fields added with `collection.addField`.
I originally found this when making the `groups` field searchable, with:
```
Users.addField([
{
fieldName: 'groups',
fieldSchema: {
type: Array,
searchable: true,
},
},
{
fieldName: 'groups.$',
fieldSchema: {
type: String,
},
},
]);
```
2018-07-23 11:59:22 +02:00
