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

Tested for data classes with fields #289

Merged
merged 1 commit into from Jan 7, 2024

Conversation

mristin
Copy link
Collaborator

@mristin mristin commented Jan 7, 2024

In this patch, we test for dataclasses which use field's to define default values. Originally, we thought that there are issues with data classes in general due to the issue #288, but it turned out that the order of decorators matters (dataclass first).

We tested everything, and documented the order of the decorators accordingly.

Fixes #288.

In this patch, we test for `dataclasses` which use `field`'s to define
default values. Originally, we thought that there are issues with data
classes in general due to the issue #288, but it turned out that the
order of decorators matters (``dataclass`` first).

We tested everything, and documented the order of the decorators
accordingly.

Fixes #288.
@mristin mristin force-pushed the mristin/Fixed-for-data-classes branch from 89c7583 to 5b1ba1e Compare January 7, 2024 21:49
@coveralls
Copy link

coveralls commented Jan 7, 2024

Coverage Status

coverage: 92.784%. remained the same
when pulling 5b1ba1e on mristin/Fixed-for-data-classes
into d6d73ca on master.

@mristin mristin merged commit 4704237 into master Jan 7, 2024
12 checks passed
@mristin mristin deleted the mristin/Fixed-for-data-classes branch January 7, 2024 22:00
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.

TypeError when using dataclasses.field
2 participants