Don't pull irrelevant keys out of the data. #40
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.
I don't have a fix for this yet, but here's a test showing that
process-set-delimiters
is doing something funny. When I use strictly to enforce that bogus keys aren't being retrieved from the map, I see that sometimes the second part of a dotted form is searched for at the top of the map.This causes me problems because I'd like to use strictly to ensure that I don't inadvertently make inconsistencies between my templates and my data (which allow me to effectively override the silent treatment of nils).
I also wonder if this problem isn't causing other observable effects - though I don't know of any personally.