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
Prefer force_registration=true in Config documentation #6259
Prefer force_registration=true in Config documentation #6259
Conversation
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.
The V2 Data Usage
block example does not have force_registration
added to it. Do we even still need that block, and does it have a reason to not use force_registration
?
@@ -304,7 +305,7 @@ the built-in Economy credits:: | |||
|
|||
class Pets(commands.Cog): | |||
def __init__(self): | |||
self.config = Config.get_conf(self, 1234567890) | |||
self.config = Config.get_conf(self, 1234567890, force_registration=True) |
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.
Should this use identifier
as a kwarg, to match other examples?
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.
Variety in examples shows that there are multiple valid ways of using the method - seems fine to me.
Co-authored-by: Michael Oliveira <34169552+Flame442@users.noreply.github.com>
Description of the changes
Adds
force_registration=True
to allConfig.get_conf()
usage examples with the exception of "V2 Data Usage" section where no defaults are registered and this may be unwanted.Additionally, I did a slight rephrasing and clarification to the documentation that mentions
force_registration=True
.Have the changes in this PR been tested?
Yes