You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The behavior of a Vase pull query does not seem to be fully defined.
Worse, it has recently changed incompatibly somewhere between Vase commits 8f61d36 and bf96190.
In the old version :find [(pull ?e [*]) ...] returned the tuples wrapped in an extra layer of vector.
This extra wrapping no longer occurs. FWIW, the new behavior seems more sensible, but the change breaks client code.
Also, surprising at least to me, a simpler :find (pull ?e [*]) returned a more complex structure. Prior to the recent changes, if I recall correctly, there were two extra layers. I've not tested what is returned in the latest version.
Suggestions:
Document the interactions between pull and Vase, and the expected values. Some additional tests would be good too. The code is likely fragile, given that the current change appears to have been introduced accidentally.
Warn that the behavior has changed, in the 0.9.1 release notes
The text was updated successfully, but these errors were encountered:
The behavior of a Vase pull query does not seem to be fully defined.
Worse, it has recently changed incompatibly somewhere between Vase commits 8f61d36 and bf96190.
In the old version
:find [(pull ?e [*]) ...]
returned the tuples wrapped in an extra layer of vector.This extra wrapping no longer occurs. FWIW, the new behavior seems more sensible, but the change breaks client code.
Also, surprising at least to me, a simpler
:find (pull ?e [*])
returned a more complex structure. Prior to the recent changes, if I recall correctly, there were two extra layers. I've not tested what is returned in the latest version.Suggestions:
The text was updated successfully, but these errors were encountered: