We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey there!
I was wondering if you guys would be open to accept a pull request which does following things:
Proposal:
Reason:
I'm using rails 6 and would like to use lines engine as it solves most of my problems, but I'm unable to since it is rails 5 only.
I don't mean directly removing devise as a whole but make it configurable by the user. Be it http authentication or custom authentication.
Reason
It seems unnecessary to bring in a complete new authentication scheme / dependencies + lines_user table if I already have a user table in my database.
I would propose to add a function call that lines calls when checking for authenticated users.
# Authentication scheme is handled and determined by the developer that uses the engine authenticate -> { |username, password| return true | false }
Kind regards Jens
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hey there!
I was wondering if you guys would be open to accept a pull request which does following things:
Proposal:
Reason:
I'm using rails 6 and would like to use lines engine as it solves most of my problems, but I'm unable to since it is rails 5 only.
Proposal:
I don't mean directly removing devise as a whole but make it configurable by the user. Be it http authentication or custom authentication.
Reason
It seems unnecessary to bring in a complete new authentication scheme / dependencies + lines_user table if I already have a user table in my database.
I would propose to add a function call that lines calls when checking for authenticated users.
Kind regards
Jens
The text was updated successfully, but these errors were encountered: