Hoàng Minh Thắng

New join api

1

Fixes #178

better api for joins

1

- join-path is not really intuitive - maybe "foreign key" is more familiar - also make it easier to customize behaviors

port the feature from older version to v1.3

make use of [guardrails](https://github.com/fulcrologic/guardrails) to give feedback of bad configuration

default props for roots/joins

2

so that ```clj [{:person/by-id] :my/join}] ;; or [{:person/by-id] [{:my/join [*]}]] ;; will behave just like: [{:person/by-id] [{:my/join [:pre/defined :default/props]}]] ```

can't use question marks in the names of pseudo-columns or aggregate-joins

1

there must be an internal automatically renaming mechanism

- lambda extra-conditions for joins - post-processing pathom plugin for columns

Implement EXISTS

1

`[:exists {:some-query-root-or-join [:table/column]}]` should expand to `EXISTS (SELECT a_column FROM some_table)` the problem is the s-expression compiler need emitter from floor-plan to compile so it should be injected to the...

- column keywords should be allowed/disallowed on a user basis, instead of just everything mentioned in `:true-columns` - `:walkble/blacklisted-keywords` is an `env` key that is injected by request handler, usually...