yeah here’s an example:

https://malli.io/?value=%7B%3Ax%201%2C%20%3Ay%202%7D&schema=%5B%3Aand%0A%20%5B%3Amap%20%5B%3Ax%20int%3F%5D%20%5B%3Ay%20int%3F%5D%5D%0A%20%5B%3Afn%0A%20%20%7B%3Aerror%2Fmessage%20%22x%20should%20be%20greater%20than%20y%22%7D%0A%20%20(fn%20%5B%7B%3Akeys%20%5Bx%20y%5D%7D%5D%20(%3E%20x%20y))%5D%5D

a very late thank you, @U051GFP2V, this is exactly what i was looking for

Is this expected behavior, Do I need wrap always on [:schema when I want to use the md/transform? it is expected that I can't pass a registry instance to a local registry and it only accept a plain map type of registries? why I can't pass the registry as options to the md/transform instead of passing the local registry to the [:schema ?

the same happens with plantuml

my sensation is that the md/transform ignores the registry passed as options

Would be nice to be able to do this:

(md/transform [:schema {:registry {"File" :app.rpc.commands.files/file}} "File"] {:registry v/default-registry})
Execution error (ExceptionInfo) at malli.core/-exception (core.cljc:138).
:malli.core/invalid-schema

After digging on it I think all is related to the pointer schema, I'm not clearly understand why it works this way:

I mean if I look up a schema with a keyword using a registry using m/schema it will return a pointer schema that will not show the form and will not walk, I need to explicit m/deref it, but I have no evident way for check if the schema is a pointer or real schema... I expect m/schema return ` real schema and not a pointer but maybe I'm missing something here that is not evident

malli.dot is not complete (and platuml is built on top of it), should add that to docs. Any improvements / rewrite of it welcome.

for pretty naming, something like a :title property could be used?

I have my own impl for openapi right now for penpot, and working on custom describe module I will show you the result when it is finished and we will see if it make sense to contribute it back to malli 😄 I have played with the dot and plantuml to understand how they works but I don't need them on the near future, maybe later

own impl to openapi? Describe module? Sounds interesting. Reitit OpenAPI3.1 support just landed on master btw

oh, I wasn't aware of that

just a screenshot, I'm right now generating the full openapi.json for the penpot rpc api this is split in two modules: one that generates the schemas for the body from malli and one custom for generate the base openapi.json structure

I mean, I have started from swagger code from malli and adapted it to openapi with probably some customizations that I need my self, just a WIP right now, I will look on the openapi support that recently landed to the malli and look on if I can use it as-is

👍 Reitit + OpenAPI was merged just few days ago, needs still testing before a release. If you have something that is missing/bad in the official impl, happy to pull them in. Also, the code is split between reitit & schema libs (malli, spec-tools, schema-tools) atm.

Ah, now I understand why I missed it, I;m not ussing reitit, I mean I use it but just for basic routing, behind that we have a classic RPC, this is why I use malli for define schemas for all metadata, and then generate openapi.json using the malli ability to walk the schemas (that is awesome)

Just a example:

we started replacing spec with malli on the codebase, and malli is just awesome

I have an old example of doing reitit + malli + rpc, just a sec…

https://github.com/metosin/reitit-example: • the web app (just looping through the actions and generating endpoints): https://github.com/metosin/reitit-example/blob/master/src/clj/example/backend/routes.clj • actions: https://github.com/metosin/reitit-example/blob/master/src/clj/example/backend/dispatch.clj

really like the command/cqrs/rpc pattern, one can program in the business/domain terms, not with http/rest. a screenshot of an app with cqrs + fsm + malli (served via reitit).

yep, very similar, we also started with query/mutation pattern but on the end we normalized all to commands, the semantic difference is that queries start the name with get-

This is the candidate output for the describe module:

FileWithPermissions -> Object {
  id => UUID,
  features => FileFeatures -> Set[String],
  hasMediaTrimmed => boolean,
  commentThreadSeqn => integer,
  name => string,
  revn => integer,
  modifiedAt => Instant,
  isShared => boolean,
  projectId => UUID,
  createdAt => Instant,
  data? => anything,
  permissions => Permissions -> Object {
    type => keyword,
    isOwner => boolean,
    isAdmin => boolean,
    canEdit => boolean,
    canRead => boolean,
    isLogged => boolean
  }
}

that i'm working on right now, it will be used for display a human readable representation of the datatype that malli schema represents