-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation for server permissions #38
Conversation
Instead of maintaining this document manually, I would prefer to keep this as a YAML document. Take a look at how "Community Links" are managed (i.e. I'd envision a structure to look like so: - permission: adminMessageReceive
description: Receives messages sent to the admin channel
# ...
- permission: actionMessage
slash-command: me
# ...
- permission: antiban
immunity-for: ban Having all of this data as YAML will allow us to easily interlink files together 😄 For example, see |
Thank you so much! I'll get to work on this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes make things a bit more verbose but it helps a lot with interlinking between data (e.g. this data file linked to slash commands automagically)
Co-authored-by: Vladimir Jimenez <allejo@me.com>
I've merged in your suggestions, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As usual, I have little insight into this framework, but I appreciate your work in adding to the documentations.
Co-authored-by: jwmelto <jwmelto@users.noreply.github.com>
Co-authored-by: jwmelto <jwmelto@users.noreply.github.com>
Don't duplicate the data between our `server_permissions` data file and our `slash_commands` collection. The collection will remain the authority with which permissions tie to said commands. Co-authored-by: The Noah <thenoahbz@gmail.com>
Group management should be handled via global groups.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your work on this @The-Noah! and thanks for being patient with us as we figured out how to organize this documentation.
Organization wise, this looks good to me. Let's wait to get feedback from others on whether or not we need more information for this PR.
I'm glad I could help, and thank you @allejo for making this 10x better! |
This is mostly complete; it just needs a few final tweaks before it's ready. I put this here so I can get feedback.
info
permission needs a description (I have no clue what this does).