Marcelo Lauxen

@cherbst-2112 @jamesbebbington As I mentioned here https://github.com/trailblazer/reform-rails/issues/86#issuecomment-758872874, I think the best approach to fix this is `reform-rails` to have its own implementation of `filter_for`, or send down to reform the...

@apotonick I think that is this what you're looking for https://api.rubyonrails.org/classes/ActiveModel/Errors.html https://api.rubyonrails.org/classes/ActiveModel/Error.html

@apotonick I'm not aware of those dotted errors, as far as I can remember in my prior job for nested forms we used `model.errors[:nested_model]`

@TarasBardiuk I think as a workaround you can use `form.errors.full_messages.any?` to check if there is any error, this will work in both cases. And to fix this issue I think...

@TarasBardiuk Even `form.errors.full_messages.any?` didn't worked when nested form validation fails? As I mentioned in my last reply, I think you could use `form.errors.full_messages.any?` instead of `form.errors.any?` as a workaround while...

Maybe a better approach will be `reform-rails` have its own implementation of `filter_for` to handle with the new ActiveModel errors API and keep using `reform` implementation for rails < 6.1...

@unavailabl3 in practice both work but each behaves in a different way, as @palexvs said, if you provide six arguments, this is what it will expect 1. seconds 2. minutes...

Mention about the support of 6 arguments added to the readme https://github.com/sidekiq-scheduler/sidekiq-scheduler/commit/58e18351054fc3c264b2b5a684173316f674c386

Can you create a sample app @jankeesvw in which we can reproduce this? It will not be enough just knowing the line it is erroring out... Stack trace, your schedule...

Thank you so much @mauricebolhuis! I will look into this issue next week along with other PRs I have on my list! I really appreciate the PR 🙏