Ashkan Nasseri
Ashkan Nasseri
@alice-letourneur the type of `instruments` field should be `InstrumentInterface`. In an example [here](https://github.com/artsy/exchange/blob/559a572e7e7f12328636d79fed59dfffbb98e28e/app/graphql/types/order_interface.rb) we define and `OrderInterface` which can be any of [these](https://github.com/artsy/exchange/blob/559a572e7e7f12328636d79fed59dfffbb98e28e/app/graphql/types/order_interface.rb#L83-L89) types. When want to expose a field...
Oh yes! I remember that now! Yes, because these types are not directly accessed in our schema, they won't be included in the final schema unless we define them as...
yes @kendallcarey , there are some examples [here](https://graphql-ruby.org/type_definitions/interfaces#definition-methods) where `price_field` is defined on the interface and has a basic implementation. Sorry about 404s, that repository this post is referring to...
Replied to you on that thread.
Also JWT one would be a good example since we learned few things along the path and we could revisit few things mentioned in that post.
Yes, that's true, as far as i understand, this only happens on collector's first inquiry when we wait for them to complete their profile and then we send it. I...
few things to consider: - This assumes we'd only have two levels of authorization, *public* or *trusted*. This is correct in case of Gravity at the moment, but just a...
yes, i 👀 too
Thanks @BenDrozdoff for reporting this 💜. Feel free to open a PR with your change or I'll try to get to this during holidays.
yes, this makes sense, a failing spec would be 👌