Skip to content
This repository has been archived by the owner on Sep 12, 2018. It is now read-only.

(tx) Support (lookup-ref a v) and (current-tx) in TermBuilder #666

Closed
ncalexan opened this issue Apr 26, 2018 · 1 comment
Closed

(tx) Support (lookup-ref a v) and (current-tx) in TermBuilder #666

ncalexan opened this issue Apr 26, 2018 · 1 comment
Labels
A-transact Issues or requests in the transactor. enhancement

Comments

@ncalexan
Copy link
Member

It's not easy to arrange, but it hurts to not be able to use lookup refs and especially transaction functions like (current-tx) (after #665) in the term and entity builders. The fundamental issue is that the meaning of a chunk of EDN given to to the transactor is context sensitive: it depends on the schema (in particular, to determine if entids or idents should be coerced to TypedValue::Ref). TermBuilder simplifies the space of value inputs, and therefore doesn't have to deal with all of the context sensitive inputs... but in turn it pays by not providing access to all of the input space.

@ncalexan
Copy link
Member Author

ncalexan commented Jul 5, 2018

This landed as part of #778.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-transact Issues or requests in the transactor. enhancement
Projects
None yet
Development

No branches or pull requests

1 participant