Clojurians Log v2

sorry if I missed something basic, but is there a way to specify that a string field should match a regular expression, without resorting to SCI functions?

@ikitommi can I trouble you for one more gist comment? this is not urgent so I’m happy to wait until your status is not “vacationing” 🙂 https://gist.github.com/stevebuik/e63735d99fca94041120f9b0e25b616d

not urgent because I can work around the perf by not using recursion in my initial spec replacements. full recursion will be useful but can come later

and because OSS should never be urgent 🙂

I wonder if I/we could turn this into a useful sample for others to learn from? happy to do this if you agree it would be useful

have you considered using :fn without using sci? why is that not a good solution?

How does malli expect bytes? to be delivered e.g. when you have a JSON api

as base64? (that would seem random)

or would one do a pass over the json, deserialize the base64 manually?

I'm asking this since babashka pods communicate via edn or json, which doesn't have a built-in way to represent bytes. transit does have it

@borkdude atm, there is no default encoding/decoding bytes and strings. Looking at OpenAPI docs, the guide is: > base64-encoded characters, for example, U3dhZ2dlciByb2Nrcw==

https://swagger.io/docs/specification/data-models/data-types/

for now I went with transit. it does it for me.. I should look into how it does it

so, there could be a byte<->string transformers in malli.transform to make this a default

workaround….

(m/validator [:schema
              {:registry {:person [:multi {:dispatch :person/gender}]}}
              :person])