Mario Celi

Sure, will do as soon as possible.

Not sure if you have control over when you call the send_confirmation_instructions method on the model, but if you do, you can do it like this ```ruby resource.send_confirmation_instructions( template_path: ['devise_token_auth/mailer'],...

@rmosolgo thank you, this helps a lot. We are going to need something similar in https://github.com/graphql-devise/graphql_devise and I think it might help for this gem too. It looks like our...

That's fine, thank you!

I was getting `Error running '__rvm_make -j8'` on Ubuntu 18.04 when trying to install Ruby 2.3.1 (got the same error for ruby 2.3.7) This fixed it as others suggested ```...

Hey @l3x4! So yes, the error won't come in the path and I'm not sure if we want that level of detail for the arguments or if even if that...

Mmm, you mean something like this: ```ruby { : errors => [{ : message => "Argument 'email' on Field 'userSignUp' has an invalid value (1). Expected type 'String!'.", : locations...

Actually the GQL gem's docs say something about it, maybe this is the best approach https://graphql-ruby.org/mutations/mutation_errors

Yes, the author of the gem recommends these kind of errors to be at the same level as data and not make them top level errors, but not sure if...

Just as an update, we have decided to implement mutation level errors field, details still under discussion, but we will probably add a setting to disable top-level errors so you...