feat: gno role manager contract

[MikaelVallenet]

No description provided.

[netlify]

✅ Deploy Preview for teritori-dapp ready!

Name	Link
🔨 Latest commit	feeefc8
🔍 Latest deploy log	https://app.netlify.com/sites/teritori-dapp/deploys/66f5671102494a0009c623bd
😎 Deploy Preview	https://deploy-preview-1285--teritori-dapp.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for testitori ready!

Name	Link
🔨 Latest commit	feeefc8
🔍 Latest deploy log	https://app.netlify.com/sites/testitori/deploys/66f56712750b430008a50cfa
😎 Deploy Preview	https://deploy-preview-1285--testitori.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[thehowl]

Took a quick look. First of all, please change the constants from ALL_CAPS to PascalCase; this is just for idiomatic Go.

Secondly, there are cases where I think maps or slices actually make sense here. Like Role.permissions. When you have small amounts of data, they can be more efficient; I suggest you play with gno test -print-runtime-metrics.

Finally, if you have a hierarchy of roles you also need a way to reorder them. So I'd suggest you leave this be for now; simply have a sudo-user owner, and then have roles modifiable by those with the correct meta-roles (role:add, etc.). (you can also go the full-length, and implement the hierarchy as you were)

[MikaelVallenet]

Took a quick look. First of all, please change the constants from ALL_CAPS to PascalCase; this is just for idiomatic Go.

Secondly, there are cases where I think maps or slices actually make sense here. Like Role.permissions. When you have small amounts of data, they can be more efficient; I suggest you play with gno test -print-runtime-metrics.

Finally, if you have a hierarchy of roles you also need a way to reorder them. So I'd suggest you leave this be for now; simply have a sudo-user owner, and then have roles modifiable by those with the correct meta-roles (role:add, etc.). (you can also go the full-length, and implement the hierarchy as you were)

Thanks for review, i think i will try to split the pkg in V2 to have the hierarchy_role_manager as an extension of the role_manager, so i can keep a very simple & straight forward version for the basic pkg. 🚀

[n0izn0iz]

superseded by #1293 feel free to reopen if needed