These are chat archives for dry-rb/chat
Next-gen ruby libs! » github.com/dry-rb » website: https://dry-rb.org » forum: https://discourse.dry-rb.org
#call. In this arrangement, you don't need to throw away your objects, and it works nicely with tools like dry-auto_inject.
includeline in the view class. i was wondering if that is the desired way of using it, @timriley ? in my world, the view shouldn't know anything about user repos?
in cells, the goal is to have views such as
%h1 = header = avatar .body = body_text
where the cell instance makes it as simple as possible to deliver the data for the logic-less view. that's basically it
class SomeView < ... include Container[:userrepo]
callwould accept runtime params and
newwould support auto-injection
human_readable_nameor something that's needed in both.
user_repodependency would be defined in two places?
gimme_some_datais redundant in the view and the json-view
Types::Strict::Bool | Types::Strict::Int | Types::Strict::String