More explicit error when trying to access the child of non-container node #444
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using ${a.b}, if
a
is not a container node, the previous code was failing with an obscure AssertionError.This commit was originally the first commit in the stack in #321 but was unrelated to other changes in that PR, so it makes more sense to create a different PR.
I don't think it's worth adding an issue and a news item for this (since it seems pretty minor) but let me know if I should.
Note: the motivation for adding
test_assertion_error()
is that otherwise coverage would drop below 100%.