Skip to content

Conversation

brandur
Copy link
Contributor

@brandur brandur commented Jul 6, 2024

Go through and add docstrings to almost the entirety of the public API,
including examples and other niceties. This should be quite helpful to
many people because VSCode renders Python docstrings when hovering over
symbols. It could also be presumably used for producing Python docs, but
I'm not going to bother with that.

Add an AttemptError data class that unmarshals itself from errors on
an insertion, although this will likely be only nominally useful since
newly inserted rows never have any errors yet.

Also, shift around some types around so they're in files named
appropriately for what they are (e.g. insert_opts.py) rather than
generic names (e.g. model.py). This also helps match the structure of
the Ruby project so that it's easier to find things.

…files

Go through and add docstrings to almost the entirety of the public API,
including examples and other niceties. This should be quite helpful to
many people because VSCode renders Python docstrings when hovering over
symbols. It could also be presumably used for producing Python docs, but
I'm not going to bother with that.

Add an `AttemptError` data class that unmarshals itself from `errors` on
an insertion, although this will likely be only nominally useful since
newly inserted rows never have any errors yet.

Also, shift around some types around so they're in files named
appropriately for what they are (e.g. `insert_opts.py`) rather than
generic names (e.g. `model.py`). This also helps match the structure of
the Ruby project so that it's easier to find things.
@brandur brandur force-pushed the brandur-doc-strings branch from d53a15f to cf152d2 Compare July 6, 2024 17:59
@brandur brandur merged commit e0874af into master Jul 6, 2024
@brandur brandur deleted the brandur-doc-strings branch July 6, 2024 18:01
brandur added a commit that referenced this pull request Jul 7, 2024
Follows up #27 to add a more elaborate test that checks that non-default
job properties can unmarshal to `Job` property including `errors, which
includes `AttemptError`. It turned out that of course this wasn't
working properly.
brandur added a commit that referenced this pull request Jul 7, 2024
Follows up #27 to add a more elaborate test that checks that non-default
job properties can unmarshal to `Job` property including `errors, which
includes `AttemptError`. It turned out that of course this wasn't
working properly.
brandur added a commit that referenced this pull request Jul 7, 2024
Follows up #27 to add a more elaborate test that checks that non-default
job properties can unmarshal to `Job` property including `errors, which
includes `AttemptError`. It turned out that of course this wasn't
working properly.
brandur added a commit that referenced this pull request Jul 7, 2024
Follows up #27 to add a more elaborate test that checks that non-default
job properties can unmarshal to `Job` property including `errors, which
includes `AttemptError`. It turned out that of course this wasn't
working properly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant