-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update 223P to public advisory review version #309
base: develop
Are you sure you want to change the base?
Conversation
beta release
…OTIF into gtf-update-223p-templates
…ugment tests to check both shacl engines
@TShapinsky I think this is finally ready for review! |
|
||
# non-singleton BuildingMOTIF | ||
class BuildingMOTIF: | ||
"""Manages BuildingMOTIF data classes.""" |
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 think this can be avoided by the following:
You can create multiple instances of BuildingMOTIF
if you call BuildingMOTIF.clean()
between each constructor call. This only deletes the current instance from the class object, you can still keep it and do stuff with it.
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.
!!! Awesome
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.
One additional thing I just thought of, you may be able to avoid the monkeypatch stuff for get_building_motif
by just setting the instance
attribute on the BuildingMOTIF
class to the one you want to use.
Looks good, @gtfierro. I have a couple more comments, but hopefully that should be it. |
There's a whole mess of changes in here, sorry! I'll summarize them here:
pyshacl
; working out how we can still test the pyshacl stuff)TODO: