How should Dry Schema and Validations be prepared with monads?

questions
1

Hey. :wave: I was trying to add a provider which would enable monad support for Dry Schema and Validation by default but finding this doesn’t error or work:

Hanami.app.register_provider :monads do
  prepare do
    Dry::Schema.load_extensions :monads
    Dry::Validation.load_extensions :monads
  end
end

I have to manually load these each time within the source code to make this work but am confused why this can’t prepared by the provider?

2

I ended up adding this to the application configuration. Example:

class App < Hanami::App
  Dry::Schema.load_extensions :monads
  Dry::Validation.load_extensions :monads
end
3

See the bottom part of my answer here for how I’ve typically done this: What is the best way to initialize dependencies? - #3 by timriley

tl;dr — create a base class in your app that all contracts, etc. inherit from, and put the global configuration in that file.

That way its only loaded when you need it, courtesy of your app’s contracts using it as a parent class.

4

I opted to respond more fully in this question but thanks for this. :bow: Yeah, I agree, this is a valid solution. A part of me kind of wants to leverage the provider lifecycle more for this because it feels more consistent but maybe that’s just me, though.