-
Notifications
You must be signed in to change notification settings - Fork 2
1st go at adding spike code to the real repo. #14
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
1st go at adding spike code to the real repo. #14
Conversation
2545f9c to
2642c2b
Compare
e31bcfe to
6316350
Compare
83d8d32 to
95eb81d
Compare
95eb81d to
376ad46
Compare
0c47338 to
e14e6ff
Compare
…ng it directly from boto.
…ng it directly from boto.
2d7c1df to
11b0f8f
Compare
37f2895 to
fae4d9c
Compare
843b5bd to
4d44ec5
Compare
4d44ec5 to
8bf173d
Compare
pyproject.toml
Outdated
| [tool.ruff.lint] | ||
| select = ["ALL"] | ||
| ignore = ["COM812", "D"] | ||
| ignore = ["COM812", "D", "PGH003"] |
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.
It's more cumbersome to include the specific type warnings, so I can understand why we might want to allow the blanket ignore, but I'd like to keep an eye on usage :D
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.
I agree.
Good spot - this one can be removed now BTW.
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.
It's specifically recommended to ignore COM812 if you are using ruff's formatting, which we are.
The "D" rules, on the other hand, we might want to discuss. Do we want to require docstrings on all classes and functions?
eddalmond1
left a comment
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.
Looks good - happy this represents what we saw in the spike but with some nice additions to our workflows
Description
Context
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.