Closed bitmage closed 10 years ago
Thanks for the clarifications!
Hm I think we usually err on encouraging use of multiple mixins instead of adding another API, so probably aren't looking for a change like that
Thanks for the PR! It's really great getting PR's on documentation. When you write code it's hard to miss what isn't clear, so it's really great getting feedback, and even better getting PRs :)
No prob!
On Jul 12, 2014, at 1:28 AM, Mark IJbema notifications@github.com wrote:
Thanks for the PR! It's really great getting PR's on documentation. When you write code it's hard to miss what isn't clear, so it's really great getting feedback, and even better getting PRs :)
— Reply to this email directly or view it on GitHub.
I added some details in the README for the multiple models example. I wasn't sure how this worked at first, and had to read the code to find out, so I figured some clarification might help.
On a tangent, have you thought about a syntax like this?
Internally it could still wire up the mixins. I don't know if it fits your style/design goals, but just figured I would throw it out there.
-Brandon