:+1:. I also noticed that the forum email notification misattributed my comment to "BrianGVose". Looks like there's a bug there.
Hi Chris - I noticed the
t.text :auth column in the migration. Was that intended to store the whole hash that comes over in case you wanted to pick it over for more data? It doesn't appear to be in use.
Hotwire is not a replacement for Webpacker but there are other gems which could replace webpacker in your project, depending on how you're using it. https://gorails.com/episodes/esbuild-jsbundling-rails
Devise is waiting on the Responders gem to update before having something standard. It pains me, but I've just disabled turbo on devise forms until there's something standard in a released version.
I still don't know what the problem was but I've followed this comment and got rid of the customizations and rendering a 422 is now working, but rendering a redirect is not. https://github.com/heartcombo/devise/pull/5340#issuecomment-833840004
I've matched what's in https://github.com/gorails-screencasts/hotwire-devise/ and I'm still not getting 422 Unprocessable Entity's rendered. When submitting an erroneous register form, the server renders the page with the form errors but the client just sits and does nothing. I've inserted a pry into the parent controller and I know that's working well. I've matched versions to
"@hotwired/turbo-rails": "7.0.0-beta.3". I'm not sure where the error is or what next to check.
Answering my own question here - the opts or args splat is not for random additional information in devise mail methods, it's specifically for headers. https://github.com/heartcombo/devise/blob/45b831c4ea5a35914037bd27fe88b76d7b3683a4/lib/devise/mailers/helpers.rb#L31
Setting up a custom invitation email with more information is how to do it. You can modify the
invite! method by passing a block. For example:
user.invite! do |user| user.skip_invitation = true user.skip_confirmation! end # NOTE We must use deliver_now to not leak invitation token to Redis CustomMailer.custom_mail_method(user, project_name).deliver_now
I'm wondering the same thing. There's a bunch of answers out there but none of them seem to leverage the built-in args* on
invite!. I can see the options being passed into sidekiq but I'm not sure how to access them in the template.
Posted in Why Ember? Discussion
There's no turbolinks 4 :P