I see the following could be a possible workaround:

(def test-schema
  (m/schema
   [::object
    [:test
     [::double]]]
   {:registry {::object (m/-map-schema)
               ::double (m/-double-schema)}}))

(m/decode test-schema {:test 1.0}
          (mt/transformer
           {:name :test
            :decoders {:map {:enter #(prn %)}}}))

Hi, there is no easy to way to do this atm as the ::object is “just a map” after schema lookup . I could add support for :type-properties into m/-map-schema so this would work:

(def test-schema
  (m/schema
   [::object
    [:test
     [::double]]]
   {:registry {::object (m/-map-schema {:type-properties {:decode/test {:enter #(prn %)}}})
               ::double (m/-double-schema)}}))

(m/decode
 test-schema
 {:test 1.0}
 (mt/transformer {:name :test}))

if that would be ok, please write issue. fix = 1 line + test.

explained: each IntoSchema can have (shared and immutable) type-properties - like Schema instances have properties. Schema application that need properties, can fallback to reading the properties from it’s parent.

Yep, that would perfectly fit our use case. We will open an issue. Thank you

Issue opened: https://github.com/metosin/malli/issues/855

Let us know if you think we could help with a PR

I had a similar experience. I found that rerunning dev/start refreshes it when registry and source change a lot in dev

In my case my source is capturing the latest state of the registry and was not updating. I suspect the watcher assumes a particular style of registry and mine is not that

Rerunning dev/start is a workaround that has worked for me. I added it to my repl fiddle forms i.e. everywhere I invoke the instrumented code

Thanks. I similarly see that it picks up the changes on re-runs, but I’m aiming to just validation all function calls at development time and I was hoping to not have to litter my code with additional calls. Also I typically just re-evaluate individual functions. Perhaps it creates a new var so it’s not instrumented? I’m sure I can hook into CIDER or have a file-watcher based solution, I’m just not certain if that’s typically needed. I appreciate the response!

Ah, I see now Malli just watches the registry, not the vars in the registry. So it seems like things are working as expected, but it’s not convenient… so I either need a workaround or to switch to a different approach that touches the registry on re-eval.

In a similar vein, if you want to instrument automated tests… any code with :malli/schema metadata not loaded at the time you enabled instrumentation would never get instrumented. So unless I’m missing something, it seems like the other instrumentation approaches are the way to go.

I suppose you could turn on the instrumentation in fixtures and it would work out fine.

Morning. It’s OK. Trying to keep protocols stable, haven’t changed much and if there is a good reason to change, it’s a minor bump (described in the CHANGELOG & https://github.com/metosin/malli#alpha documentation.

e.g. part of the extender API

Great! Thanks for your feedback.