feat: call map-key w/ parent-schema information #119
Conversation
This commit passes the parent-schema (ie. the map) to get the transformer
function.
This is useful if your map-keys wants to introspect the schema to determine
its behavior. An example usecase would be automatically remove the most
prevelant namespace of a key, and adding a string underscore encoding
for other namespaces. Eg. you can use this to write a json encoder that
does something like the following:
```clj
{:person/name "Bob" :person/age 36 :pet/name "Edgar"}
;; =>
{"name" "Bob" "age" 36 "pet_name" "Edgar"}
```
|
Thanks for the PR. I'm not happy about this breaking the contract of having There is a discussion about having a link to the parent from all schemas, which would, I believe, solve this without breaking the contract. Collected info into an new issue #120 |
|
Makes sense! It definitely felt dirty but since For my use case, I can get away with not having it once #122 lands - moving the functionality into the |
This commit passes the parent-schema (ie. the schema of the map) to get the transformer function used in map-keys.
This is useful if your map-keys wants to introspect the schema to determine
its behavior. An example usecase would be automatically remove the most
prevelant namespace of a key, and adding a string underscore encoding
for other namespaces. Eg. you can use this to write a json encoder that
does something like the following:
{:person/name "Bob" :person/age 36 :pet/name "Edgar"} ;; => {"name" "Bob" "age" 36 "pet_name" "Edgar"}