just slicing things into pieces would be enough
btw I’m gonna start working on the book in the upcoming week(s)
first things I need to figure out is dir/file organization for it
Have a look at that repo i gave you access too
my container has grown into lots of things but it’s
Foo.new in 90% of the cases
If we had auto curry we could always new up and then just configure the arguments
Although i guess instantiation isnt always what you want
idea of controllers and messing with response object
Thats how i use ut tho
class FormAttributes < Dry::Data::Struct
def self.new(attributes)
schema_defaults = schema.keys.map { |key| [key, nil] }.to_h
super(schema_defaults.merge(Hash(attributes)))
end
def [](attribute_name)
send(attribute_name)
end
end
Just so it's not so strict about missing values when initializing
and
#[] in place so I can use it with a ROM::Model::Validator
App.register "transformations.to_h" do |input|
input.to_h
end
App.register("transactions.sign_up_customer") do
CallSheet(container: App) do
map :process, with: "attributes.customer_sign_up"
try :validate, with: "validators.customer", catch: ROM::Model::ValidationError
map :prepare_for_persist, with: "transformations.to_h"
tee :persist, with: "persistence.commands.create_customer"
end
end#to_h to that FormAttributes class and that prepare_for_persiststep in the business transaction.
Does not feel ideal, but it works for now at least ¯_(ツ)_/¯
first cut of this lib is targeting defining domain data types, as the second step I was planning to work on form-specific logic (with custom builtin types/coercions dedicated for this concern)
@AMHOL would be nice to put together a roadmap for dry-* gems so that we can see the big picture and hopefuly get more people contributing; from my pov validation + data are currently number 1 prio, but there are also some things that we could improve in dry-container and auto_inject (actualy thinking about renaming it to dry-import)
ugh, sorry, I meant that number 1 prio is GETTING A LOGO FOR THE ORG :joy:
@AMHOL is this expected?
this one will be inherited
but the configured settings won't