tianrking
In statically typed ecosystems the compiler catches a lot of mistakes. In Rails ecosystems the safety net historically became tests + conventions.
The problem shows up once the codebase gets large and those conventions start to drift. At that point the compiler would have been a very useful backstop.
That's probably why a lot of long-time Rails developers still love it for small teams and product work, but feel friction once the codebase crosses a certain size.
If the UI asks a yes/no question, the “no” should be enforced as a state transition that blocks write actions, not passed back into the model as more text to interpret.
Once “permission” is represented as tokens instead of control flow, failures like this are almost inevitable.
The model failure is funny, but the bigger bug is that the system treated consent as prompt material instead of as a hard gate