I hear you
^ magic here ;]
@timriley your blog posts and repos was a HUGE help
it's so kard to glue everything together for the first time, a lot more blog posts and docs needed
@gotar yeah, I hope I can write some more stack-specific docs over the next 2 weeks. And my blog posts... Well, they'll get there eventually. They have a plodding pace :)
because ROM::Relation do not works with basic one -
Container::Inject
or hack
root for rom::repo, to have base class to limit code repetition, like: https://github.com/gotar/dry-web-skeleton/blob/master/lib/persistence/repo/base.rb#L15
probably other places too, like class around dry-v schema to make it AutoInjectable
so it's gonna be tough to explain to people who mostly know rails
we will see
I already told them something about roda and rom, but they never wrote any app outside rails
then I plan to write some basic roda + rom app, and then go deeper and deeper inside container, auto-inject ...
we will see
hanami will be a much much better "entry point" for people, I think
hard for them to force themself to try at home
then will will try this way, evangelistaion all the time ;]
ok time to sleep, bye and thx for great support as always :)
:wave:
What you are doing with that AutoInject hack is actually a lot nicer with dry-component's injector. But I'll see if we can improve the base AutoInject too
With dry-component you can just switch strategies ad-hoc
e.g. include MyComponent::Inject.args["foo"]
;)
I’ll add an issue to remind me to do that to dry-auto_inject directly
And I’ll release dry-component today :)
@gotar I think I have a fix for your repo issue
what if you got rid of this: https://github.com/gotar/dry-web-skeleton/blob/master/lib/persistence/repo/base.rb#L14-L16
And changed
class Posts to be class Posts < Base[:posts]
and change
class Base to be class Base < ROM::Repository::Root