Very glad to hear that. I really resisted going in this direction because of the apparent decrease in flexibility. I even briefly considered adding a good amount of extra code to make a backwards “compatiblish” syntax where the options could be passed in a separate 3rd argument to admin_resource. I guess I would still consider that if people request it, but eventually I ended up admitting that in my own use I was either not passing any options at all, in which the line in the schema seemed fine, or the options came with custom functions that–being admin specific–felt really wrong in the schema and so needed a dedicated module anyway.
1 Like
