Adrian Marin

I understand the confusion with `disabled`, but the truth is that the `has_one` has more than just one state. A user can attach/detach/create records on it, so that's why we...

You can set the `via_per_page` globally [right now](https://docs.avohq.io/3.0/customization.html#resources-via-per-page:~:text=For%20has_many%20associations%20you%20can%20control%20how%20many%20resources%20are%20visible%20in%20their%20Index%20view%20with%20config.via_per_page%20%3D%208). Otherwise, IDK is `self.via_per_page` would do it justice. I would rather do the first option: ```ruby field :certifications, as: :has_many, per_page: 72...

If the global configuration is enough for you, @smathieu, then it's ok to close this issue. If you need something more granular, we'll merge a PR with that. Unfortunately, we...

Got it! Yes, the field config should work better from the same reason that you want to configure the per_page only in some scenarios. I added the `Help wanted` label....

Yes, let's do that in development! As a separate feature, we should also create the concept of "super-admin" or something where we would show that error in production to those...

Can you please give more details? I can't quite get it from your description

No worries! We would love to support this use case. Do you think you'd like to contribute this feature? We'd love to merge a PR. We'll even help you navigate...

hey @m7madmagdy, thanks for the suggestion. That would be a cool and useful thing to support. We're open to having that 1st party. Would you be open to doing some...

Yes. Through JS, they can attach handlers similar to how we do it now in `avo.base.js` with the `m m m` shortcut

Maybe use something like this? https://github.com/marcoroth/formulus