juxt/aero

Tags do not resolve in an obvious order.

mchughs opened this issue · 4 comments

The two following code blocks will have different values associated with the key :result.

{:foo {:bar "my-value"}
:result #ref [:foo #keyword "bar"]}

will resolve to the map

{:foo {:bar "my-value"}
:result nil}

where as

{:foo {:bar "my-value"}
:my-key #keyword "bar"
:result #ref [:foo #ref [:my-key]]}

will resolve to the map

{:foo {:bar "my-value"}
:my-key :bar
:result "my-value"}

My expectation would be that the output maps should be the exact same. (other than for the :my-key :bar key-value pair) I ideally shouldn't have to create an intermediary key to work-around reader composition rules.

Just to check, what version are you using? I wouldn't expect to see this in the latest version.

Just tested with 1.1.4, and this is working.

Ah I was using 1.1.3 my mistake.

No problem. This was one of the things resolved in that, and it was only recently resolved.