<div dir="ltr">@andrew to answer your questions:<div><br></div><div>1) A Rails controller's public API should be only action methods therefore defining extra public methods is a bad idea as they become routable. Not to mention interface segregation is always a good thing and as I mentioned Forwardable and SimpleDelegator let you whip up adapter objects very easily.</div>
<div><br></div><div>2 and 3) Good code samples are *hard* to write, I'm working on some but this post is my MVP based on conversations I've had with various people. I will endeavour to provide some ASAP.</div><div>
<br></div><div>On the point of "considering other Rails users" I feel that why and how of clean architecture are two different but related arguments, I only really wanted to have to latter today :)</div><div><br>
</div><div>Bestie.</div><div class="gmail_extra"><br><div class="gmail_quote">On 18 March 2014 15:42, Andrew Premdas <span dir="ltr"><<a href="mailto:apremdas@gmail.com" target="_blank">apremdas@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im HOEnZb">Some questions/points:<br>
<br>
1. Why can't the controllers be the RailsAdapter?<br>
<br>
2. The article needs to show app_of_things. It isn't clear for example<br>
that when you write a foo controller there will be an app_of_foo. Also<br>
see 1<br>
<br>
3. The article needs to show rails_adapter, and show the mechanism<br>
used for it to make sense in the controller.<br>
<br>
I think you need to consider other rails users when you go so far from<br>
the norm. In particular the code in the controller should guide the<br>
programmer to the correct place. I'm not convinced that a variable<br>
does this. That single line of controller code is how you introduce<br>
this new hexagonal world it deserves more attention.<br>
<br>
</div><div class="im HOEnZb">All best<br>
<br>
Andrew<br>
<br>
On 18 March 2014 11:15, Stephen Best <<a href="mailto:bestie@gmail.com">bestie@gmail.com</a>> wrote:<br>
</div><div class="HOEnZb"><div class="h5">> I have a blog post that is currently enjoying a fleeting moment of exposure<br>
> via a questionable "news" for "hackers" outlet. Would love to hear LRUG's<br>
> feedback.<br>
><br>
> <a href="https://news.ycombinator.com/item?id=7421018" target="_blank">https://news.ycombinator.com/item?id=7421018</a><br>
><br>
><br>
> Stephen Best<br>
><br>
> <a href="http://theaudaciouscodeexpiment.com" target="_blank">theaudaciouscodeexpiment.com</a><br>
> <a href="http://github.com/bestie" target="_blank">github.com/bestie</a><br>
> @thebestie<br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> Chat mailing list<br>
> <a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
> <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
><br>
<br>
<br>
<br>
--<br>
------------------------<br>
Andrew Premdas<br>
<a href="http://blog.andrew.premdas.org" target="_blank">blog.andrew.premdas.org</a><br>
_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
<a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
</div></div></blockquote></div><br></div></div>