-
Notifications
You must be signed in to change notification settings - Fork 138
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
[issue-290] refactor data model #298
[issue-290] refactor data model #298
Conversation
e26db6f
to
fcac984
Compare
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 overall structure looks promising, but there are a few remarks from my side.
As this will be the basis of all following work, I tried to be quite strict. ;)
e0a0014
to
b9c3456
Compare
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.
That seems to be it!
Don't forget to squash! :)
Signed-off-by: Nicolaus Weidner <[email protected]>
Signed-off-by: Nicolaus Weidner <[email protected]>
Signed-off-by: Nicolaus Weidner <[email protected]>
Signed-off-by: Nicolaus Weidner <[email protected]>
Signed-off-by: Nicolaus Weidner <[email protected]>
Signed-off-by: Nicolaus Weidner <[email protected]>
3022dbe
to
2a3a80c
Compare
Fixes #290
Rewritten data model, hopefully clearer in particular with regards to types. It's fairly minimal so far, we can add more utility later (e.g. more magic functions)
Note: As soon as the Python min version is officially 3.7, we can check whether dataclasses can reduce some of the annoying duplication involved in writing constructors, for example.