This adds the command_attrs parameter to the commands.check decorator and reworks a lot of checks in order to allow introspection later of attributes like Command.required_permissions.
Checklist
If code changes were made then they have been tested.
I have updated the documentation to reflect the changes.
This PR fixes an issue.
This PR adds something new (e.g. new method or parameters).
This PR is a breaking change (e.g. methods or parameters removed/renamed)
This PR is not a code change (e.g. documentation, README, ...)
<!-- Pull requests that do not fill this information in will likely be closed -->
## Summary
<!-- What is this pull request for? Does it fix any issues? -->
This adds the `command_attrs` parameter to the `commands.check` decorator and reworks a lot of checks in order to allow introspection later of attributes like `Command.required_permissions`.
## Checklist
<!-- Put an x inside [ ] to check it, like so: [x] -->
- [x] If code changes were made then they have been tested.
- [x] I have updated the documentation to reflect the changes.
- [ ] This PR fixes an issue.
- [x] This PR adds something new (e.g. new method or parameters).
- [ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
- [ ] This PR is **not** a code change (e.g. documentation, README, ...)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
This adds the
command_attrsparameter to thecommands.checkdecorator and reworks a lot of checks in order to allow introspection later of attributes likeCommand.required_permissions.Checklist
I'm confused as to why this exists, adding command attrs inside a check seems like a niche usecase, does the library really need to handle this
This is so things like
Command.required_permissionsis possible to access + allow user checks to add similar attributes