> The only way to have `nav` selectively recognise keys based on their
> existence in the map, is to put its whole logic behind a `contains?` check.
> However that sounds counter-intuitive/productive...
Remember that nav is called with the key _and the value_ so it will be passed
whatever
On 10/02/2020 20:45, Sean Corfield wrote:
I’m suggesting that if you add certain key/value pairs to the datafied
Java Time values, nav could recognize those as navigation from data to
“stuff”. This gets you much closer to your original concept while
staying within the datafy/nav confines.
> Ok, I'm glad datafy/nav works as expected, but the rest of you response
> confuses me again :)
Sorry ☹
> You now seem to implying going back to "doing too much" with `nav` - or have
> I misunderstood you (again)?
I’m suggesting that if you add certain key/value pairs to the datafied Java
Ok, I'm glad datafy/nav works as expected, but the rest of you response
confuses me again :)
The reason I removed support for navigating to `:format` was because we
established in previous conversations that I was doing too much with
`nav`. I was using it for comparing, shifting, formatting &
