-
Notifications
You must be signed in to change notification settings - Fork 6
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
Assignments should strip off any ConfigNode wrappers. #15
Comments
Nested containers remain an
|
Yeah, I feel like this is a tough one. Like we talked about: I feel like the answer might want to be "you should be using the mapping/merging APIs" but want to leave this open for the next time I have a proper chance to play with this project... |
I noticed that
Config.__eq__
isn't implemented so we just getobject.__eq__
comparison (identity based)Would it be possible to get a content-based equality comparison? In the simple example above we could just use
c1.data == c2.data
, but my real use-case has a nested configuration so comparing data attributes doesn't work either: the nested values are instances ofConfigNode
, which also has identity-based comparison.My use-case is in testing comparisons, where we want to assert some configs from multiple sources have been parsed and layered the way we expected, without having to recursively extract all the content from the
Config
instance. i.e., just compare with an "expected"Config
orConfigNode
instance directly.The text was updated successfully, but these errors were encountered: