Open MrJoy opened 11 months ago
Because custom tools are very much regular Rails code, we presumed that users will move that route into their routing scheme anyway.
But you have a good point. I added the "Help wanted" label. Hopefully, someone can contribute this feature.
I can look after it @adrianthedev if it's still available.
Thank you @enderahmetyurt!
Could we pause this for now? I'm uncertain whether we should move forward with it.
devise
) when Avo doesn't actually require it?devise
specifically) but others might want an info page that's accessible to everyone or another authentication methodIn my opinion, we should keep the route generation stupid simple. The goal is to provide a starting point that you can customize as needed, rather than delivering a fully finalized solution.
Describe the bug
When using
rails generate avo:tool
, the update to routes.rb produces a route that is not protected by Devise.Specifically, it produces:
This should be within an
authenticate
block.Steps to Reproduce
Steps to reproduce the behavior:
rails generate avo:tool my_tool
Expected behavior & Actual behavior
Models and resource files
System configuration
Avo version: 3.0.1.beta20
Rails version: 7.0.8
Ruby version: 3.2.2
License type:
Are you using Avo monkey patches, overriding views or view components?
Screenshots or screen recordings
Additional context
Impact
Urgency