zauberware/rails-devise-graphql

A Rails 6 boilerplate to create your next Saas product. Preloaded with graphQL, devise, JWT, CanCanCan, RailsAdmin, Rubocop, Rspec, i18n and more.

rails-devise-graphql's Issues

Rails 6

Bump to rails 6

How can I implement apartment gem with this boiler?

Hello team,
Thanks for your boiler, It's very helpful, but I want my website has multiple tenants, so how can I implement an apartment gem with this boiler?

Please give me a guide or some information.
Thank you in advance!

Error when user does not exist

Hi guys,

I've got an error when I'm using the signIn mutation and provide false credentials.
The user does not exists and it raises this exception :

undefined method 'lock_strategy_enabled?' for nil:NilClass

It comes from your fork of the gem graphql-auth on branch rails6 where no verification is done about user existence

Have a great day :)

QUESTION: Updating to rails 7

Hi,
I'm very interested in this repo since i'd like to to a project but i do use rails 7
(Quite fresh to Ror, like 1 year) so I wonder if anyone attempted to do it ?

Prefered Authentication gem? devise_token_auth?

Dear rails and graphql community,

many thanks for more than 200 stars on github! This is amazing! 💙

Maybe you could help us out in decision making: Would it be better to integrate devise_token_auth as token authentication method.

The truth is that we dropped the current graphql-auth gem in our other projects. We are using devise_token_auth there and it works very well.

thank you1

Error handling on user mutations?

I've started to play around with this project a bit more and I'm curious if there would be appetite to have error handling added into the user mutations? For example, the SignUp mutation doesn't handle a lot of the common signup errors (account exists, invalid pw length, etc.)

Not sure how far you want this project to go in terms of boiler plate. I'm already adding the common error handling scenarios to a small hobby project I'm working on, so I would just flip them back into this repo. Let me know and I can start contributing back (similar to #7).

`current_user` not being set in context

I'm noticing that upon signing in via GraphQL, the current_user property is not available within context. The steps I've taken are:

1. Sign up

mutation {
  signUp(email: "[email protected]", password: "lol12345", passwordConfirmation: "lol12345") {
    user {
      id
    }
  }
}

2. Sign in

mutation {
  signIn(email:"[email protected]", password: "uniiverse", rememberMe: true) {
    user {
      id
    }
  }
}

3. Query the "Me" field. The underlying field retrieves the context[:current_user]

query	{
  me {
    firstName
  }
}

Devise confirmable

Please add devise confirmable to graphql implementation.