Skip to content
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

react-to-role resolution #257

Open
sinus-x opened this issue Feb 8, 2021 · 0 comments
Open

react-to-role resolution #257

sinus-x opened this issue Feb 8, 2021 · 0 comments
Labels
bug Something isn't working server members offer Member solving this issue will be rewarded on our server
Milestone

Comments

@sinus-x
Copy link
Owner

sinus-x commented Feb 8, 2021

When you have access to the channel and use the # sign, it is saved as channel reference <#123> instead of just plain readable string #foo. As a result, the bot does not find the channel, because it's looking for <123> and not foo.

Solution is not using hash signed names (channels take precedence over roles). To distinguish roles and channels, we can make a mapping (json dict or database), that would map a channel to either roles or channels and wouldn't look for anything else. We could also add an ACL check, so only users with given ACL group would be allowed to get their requested access.

@sinus-x sinus-x added the bug Something isn't working label Feb 8, 2021
@sinus-x sinus-x added this to the v1.3 milestone Feb 8, 2021
@sinus-x sinus-x added the server members offer Member solving this issue will be rewarded on our server label Mar 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working server members offer Member solving this issue will be rewarded on our server
Projects
None yet
Development

No branches or pull requests

1 participant