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
Should emit the name of the service which was updated. This will allow cogs to cache the values and only update when if they change.
The text was updated successfully, but these errors were encountered:
on_red_api_tokens_update
Doesn't config already use a cache? Also, would it be worth expanding the event scope to consider config changes overall?
Sorry, something went wrong.
Config doesn't cache for DB backends. This is one of the only places 3rd party code might be caching a setting in nonobvious way (such as a single aiohttp client session) and should receive an indication to update
Successfully merging a pull request may close this issue.
Feature request
Select the type of feature you are requesting:
Describe your requested feature
Should emit the name of the service which was updated. This will allow cogs to cache the values and only update when if they change.
The text was updated successfully, but these errors were encountered: