relations with arguments not showing up on model about mst-gql HOT 9 CLOSED

I run into the same issue. It seems that resolveFieldsAndImports() in generate.js explicitly filters out fields with arguments.

Is this necessary, is there any reason for this behaviour? If so, then can this be made optional?

from mst-gql.

I'm not sure if there is a reason behind this (@mweststrate?) and haven't had a chance to dig in myself yet.

from mst-gql.

Until someone can clarify this I added a --allowFieldArgs option to the generator and created a pull request in case this turns out to be useful.

from mst-gql.

@beepsoft does it seem to work without issue with args?

from mst-gql.

Yes, in my app it seems to generate the approriate definitions and when querying via the store it fills these properties correctly. In my cases these are arrays of objects. If the type is specified as root with --root Foo

then I get

bar: types.optional(types.array(MSTGQLRef(types.late(() => FooModel))), [])

otherwise

bar: types.optional(types.array(types.late(() => FooModel)), [])

I think that's how it is supposed to work.

from mst-gql.

If this is the case I see no reason not to make it the default :)

from mst-gql.

Yep. :-)

from mst-gql.

@chrisdrackett Can you please fix this by deleting that filter line?

from mst-gql.

I’m currently out of town. The earliest I could get to it is Tuesday.

from mst-gql.