-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add util functions extracting end_user_data_statement
directly from cog's info.json
#4404
Add util functions extracting end_user_data_statement
directly from cog's info.json
#4404
Conversation
I'm a fan of anything that means I don't have to store the same text twice. |
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.
Aside from various grammar stuff and other small issues that I pointed out in review comments, the methods are called get_end_user_statement
rather than get_end_user_data_statement
which doesn't make that much sense when you read it (as in: it's a statement about end user data, not statement about end user). If you think that it's too long name, I guess we could also call it get_eud_statement
, although I'm not really all that convinced that it's a good name.
Co-authored-by: jack1142 <6032823+jack1142@users.noreply.github.com>
Co-authored-by: jack1142 <6032823+jack1142@users.noreply.github.com>
This should now be ready to merge |
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.
LGTM
end_user_data_statement
directly from their info.json
end_user_data_statement
directly from cog's info.json
Type
Description of the changes
here is an example usage of this new util.
This util will attempt to read the statement directly from the cogs
info.json
and if not successfull it will log a meaningful message to the user letting them know its not possible to do so and at that point it will returnNone
so that the default handling will be handed back to Red (It will mention that this cog does not have an end user data statement in the[p]3rdparty
command).