by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 31 11:56
    serodriguez68 labeled #147
  • May 31 11:56
    serodriguez68 opened #147
  • May 30 17:35
    aka-emi starred dry-rb/dry-monads
  • May 30 09:18
    k0va1 opened #71
  • May 30 08:37
  • May 29 21:51
    armstnp closed #125
  • May 29 21:51
    armstnp commented #125
  • May 29 20:27
    sankalpk starred dry-rb/dry-types
  • May 29 14:43
    josh-dev-test starred dry-rb/dry-types
  • May 28 16:39
    kietnguyen starred dry-rb/dry-types
  • May 27 09:03
    Travis dry-rb/dry-transaction (release-0.13) errored (353)
  • May 26 18:01
    marzdrel starred dry-rb/dry-system
  • May 25 09:50
    k0va1 starred dry-rb/dry-monads
  • May 22 10:57
    solnic commented #146
  • May 21 22:24
    armstnp edited #125
  • May 21 22:23
    armstnp edited #125
  • May 21 22:17
    armstnp labeled #125
  • May 21 22:17
    armstnp opened #125
  • May 21 10:54
    jezstephens commented #146
  • May 21 09:25
    solnic labeled #146
Tim Riley
@timriley
Right. So a more formal approach to what we kind of have with our "boot" stuff atm, except built around whole components?
Piotr Solnica
@solnic
yeah, it’s about making things organized better
Tim Riley
@timriley
I would like that
Piotr Solnica
@solnic
system(:persistence).boot! triggers loading and booting of its components
we just miss an explicit concept of a system
then you could share systems across apps…
they would be contained
Tim Riley
@timriley
Right! Yeah, I like this. Atm it is awkward that our "top level" in dry-web is a component like everything else. It felt like it needed to be a bit different
Piotr Solnica
@solnic
this really boils down to managing state in an app :)
Tim Riley
@timriley
Haha, right
Piotr Solnica
@solnic
db connections, http clients, all this stuff
Tim Riley
@timriley
Hmmm, so should I investigate that clojure lib, watch that talk? I feel like I need to research some more.
Piotr Solnica
@solnic
yeah it’s worth exploring, good news is - ruby is better suited to handle this stuff :)
Tim Riley
@timriley
(This might need to be a medium-term thing - before RDRC I'd like to see if I can just smooth some rough corners in what we already have)
Piotr Solnica
@solnic
yep
Tim Riley
@timriley
Since there's not that long until then.
Cool. Well, I'll write up some notes about that on Sun or Mon :)
Piotr Solnica
@solnic
another good example of a system would be http routing
basically entire http front-end can be contained within a system
Tim Riley
@timriley
Yeah, that feels better
Piotr Solnica
@solnic
ie hanami router + rack + middlewares == http system
Tim Riley
@timriley
It shouldn't be some exceptional thing
Piotr Solnica
@solnic
you just plug it into your app, the top-level system
Tim Riley
@timriley
And that http system would depend on the app's system?
Piotr Solnica
@solnic
another one, view rendering, also a system
no it shouldn’t know about the app’s system
it’s plugged into it
I think, thinking out loud :)
the integration point is the app’s container, which provides the app’s API to the http front-end
that, we already have, it’s just about making this more formal with better vocabulary :)
and an explicit object representation
Tim Riley
@timriley
Hmm, right
Yeah, I get this
(The role of the container to connect things)
Piotr Solnica
@solnic
it’s gonna be really cool to build a tool that looks at your setup and generates a visual representation of what happens when a request comes in :D
rack middlewares => final routing end-point => application end-point => specific objects that process data => perrsistence operations => db result => app result => http response
Oskar Szrajer
@gotar
NewRelic^2 ;]
Piotr Solnica
@solnic
right, this would be taken to the next level
esp with monitoring capabilities
Tim Riley
@timriley
Oh man, Michael at Icelab would love this
Piotr Solnica
@solnic
:)
Oskar Szrajer
@gotar
idea for product - $$$
Hannes Nevalainen
@kwando
@timriley more customizable / less restrictive auto_registration for dry-component would be nice, read that you were going to spend some quality time with dry-component =)
Worth a watch if anyone hasn't seen it yet
Piotr Solnica
@solnic
@kwando if you don’t like default behavior just register your objects yourself
I wouldn’t want dry-component to turn into a highly customizable object construction framework
Hannes Nevalainen
@kwando
@solnic I already got my own registration strategies
some of them is rather app specific though
Maciej Mensfeld
@mensfeld
@solnic will there be a strict mode for dry-validations? I mean now I can pass a field that I haven't declared and it is there