Loved this video and I appreciate the tips about using the main branch and getting access to this feature I wonder if there is a good tailwind template or that woudl be a good idea for a new gem
I like to reuse the same conventions as the ones used in Devise. So usually I will have current_user and same for the methods so that I can reuse other gems without any charge (Authorization or Access control for example)
@@SupeRails Pundit is one. Also many examples for Rolify are based on the Devise conventions (unlike Pundit, I do not think that they are enforcing the conventions)
🚨 The updated syntax is to use `bin/rails generate authentication`, not `bin/rails generate sessions`
Finally! Something that make more sense than fight with JS...
In what case are you fighting with JS on authentication?
@@SupeRails I mean make more sense, since everyone need auth. And JS keeps changing…
Great. Thanks for useful info.
テストするまでは今まで通り自前のログイン機能かdevice使い続けると思うけど新しい認証増えてるのは嬉しい😊
To be clear, I do not recommend you to use this new Rails auth generator. Devise is way better!
Loved this video and I appreciate the tips about using the main branch and getting access to this feature I wonder if there is a good tailwind template or that woudl be a good idea for a new gem
There's a place for that! github.com/rails/tailwindcss-rails/issues/382
Hilarious thumbnail 😄
Great video 👍
Thanks bro. Although it's a bit misleading. Devise is very good, and it's going nowhere any time soon!
Спасибо Ярослав за интересное и познавательное видео.
все для вас, дорогі друзі :)
Is there any good reason to do this? Is the Devise gem dead or troublesome in some way?
No, I do not recommend to use this solution! Devise is perfectly good. I recommend Devise!
Great!
great video, do you think apart from basic authentication rails would implement oauth out of thee box?
I really really doubt that
Finally!
I think we still need to wait a bit for this to be production-ready
I like to reuse the same conventions as the ones used in Devise. So usually I will have current_user and same for the methods so that I can reuse other gems without any charge (Authorization or Access control for example)
I also like the devise naming. But.... I don't recall of any other gems that rely on having methods like "current_user"...?
@@SupeRails Pundit is one. Also many examples for Rolify are based on the Devise conventions (unlike Pundit, I do not think that they are enforcing the conventions)
So what you do for oauth?
@@tofuman9526 OAuth2 gem or doorkeeper.
What about OAuth implementation?
Check out episode #103 Simple Omniauth without Devise. That's what I use for superails.com/