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

plugin classes should not access DEFAULT_PARAMS #906

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

jmartin-tech
Copy link
Collaborator

DEFAULT_PARAMS are projected onto instances by Configurable and should not be directly access from the dict CONSTANT in class methods. If the user provided configurtion that overrides the default the user value is found on the instance.

`DEFAULT_PARAMS` are projected onto instances by `Configurable` and should not
be directly access from the `dict` CONSTANT in class methods. If the user provided
configurtion that overrides the default the user value is found on the instance.

Signed-off-by: Jeffrey Martin <[email protected]>
Copy link
Collaborator

@leondz leondz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch, thanks for tagging me to review this.

hoping that addressing #883 will reduce the chances of things coming in.

i would like one day to get test warnings/failures for things like:

  • commits that introduce print() stmts
  • mentions of DEFAULT_PARAMS in functions in plugins

@leondz leondz merged commit 237372f into NVIDIA:main Sep 9, 2024
8 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Sep 9, 2024
@jmartin-tech jmartin-tech deleted the fix/improper-defaults-access branch September 9, 2024 13:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants