dkubb changed the topic of #datamapper to: Datamapper v1.2.0 | Mailing List: http://is.gd/aa9D | Logs: http://is.gd/qWAL7V | DataMapper 2 Renamed to ROM, see #rom-rb for development
v0n has joined #datamapper
v0n has quit [Ping timeout: 245 seconds]
stormwind has quit [Read error: Connection reset by peer]
stormwind has joined #datamapper
skade has joined #datamapper
skade has quit [Quit: Computer has gone to sleep.]
<lgierth>
in this case it's just issues with managing github issues over multiple repos though
<dkubb>
we have that issue
<dkubb>
as long as we keep things decoupled that's the main thing I care about
<dkubb>
I'd hate to gravitate towards a monolithic design where every component depends on every other component
<dkubb>
like with rails where theoretically you can strip some pieces out, but in practice no one does so you run into weird dependency bugs when you try
<lgierth>
i'm totally +1 with everything said in the comments
<dkubb>
lgierth: btw, we're in #datamapper now, not #rom-rb ;)
<lgierth>
ouh!
<lgierth>
having #datamapper marked as having new lines must have confused me!
<lgierth>
develop7: you can define properties from whereever you want, but make sure to do it only before calling DataMapper.finalize (not during actual runtime, that is)
skade has quit [Quit: Computer has gone to sleep.]
kleech has quit [Remote host closed the connection]
lfox has joined #datamapper
skade has joined #datamapper
<develop7>
lgierth: I do and Datamapper considers Stuff module a separate model, while I want to be able to mix Stuff into multiple DM resources classes.
<lgierth>
develop7: oh i see what you mean, i hadn't looked at your code