newbie here. I watched @timriley's Singapore presentation and really liked the functional-ity and separation of concerns. I'm looking for some convention to surround me as I get started with these new-to-me dry and rom capabilities. Something like a "click here to download Trailblazer with skeleton support for a Riley-like dry/rom app".Is there any getting-started resource like that? Maybe @fran-worley can recommend where someone new to both dry/rom and Trailblazer should start if they have no legacy app to evolve?
I'm really interested in the ROM Relations concept that allows architect/developers to work with objects that look like business objects rather than detailed database scaffolding because the kind of applications that I work on have complex object-with-object relationships and all relational database repositories eventually so pollute the network-graph business concepts that the business services often have to be simplified or be reduced in flexibility if the relational-model details are implemented in the business objects themselves. Therefore, the dry/rom architecture of separating out associations as proper objects, of separating out repository query handlers, of separating out functional dependency-injected command objects, from the business objects themselves is intoxicating.
truey?doesnt exist built in
dry-web-roda generate entity MY_NEW_ENTITYgeneration script that helps one seed a new entity into the terraformed directories? For example, if I have just raygunned out a new dry-web-roda app from the skeleton, what's the next step to, say, add a route and view for a first-pass-do-nothing entity of "Tweets"? (This is likely all very evident for someone very familiar with the whole stack, conventions, and traditions but isn't evident to a newcomer or, at least, to me.)
system/my_app_name/application.rbto the following:
module MyAppName class Application < Roda route do |r| r.on 'admin' do r.run Admin::Application.freeze.app end r.run Main::Application.freeze.app end end end