#go Rails Engines
2015-04-01 10:38 GMT+00:00 Ecleel :
> I'd love to see more use for Rails Engine and make it a default way of
> developing application.
>
> On Tuesday, November 25, 2014 at 5:09:57 PM UTC+3, Jason FB wrote:
>>
>> Rails core,
>>
>> I was wondering if Rails 5 has a discussed (or pr
I'd love to see more use for Rails Engine and make it a default way of
developing application.
On Tuesday, November 25, 2014 at 5:09:57 PM UTC+3, Jason FB wrote:
>
> Rails core,
>
> I was wondering if Rails 5 has a discussed (or proposed) roadmap? A
> growing chorus of developers are seeking way
Hello,
I've been giving a lot of thought to building a gem which puts more
validation into the controllers and routing and removes it elsewhere. My
conclusion was that I didn't need to build a gem, Rails in fact already has
everything needed to accomplish this, however - I just need to change t
BTW, something that is in the radar is replacing
accepts_nested_attributes_for with something else, maybe form objects... it
is just being explored (and could end up in nothing).
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscr
While we are on the subject of potential changes, I asked in a previous
thread about what's gonna happen to controller tests (functional tests in
previous parlance) and got no response. I am asking for two reasons: 1. It
was one of the proposed GSOC projects, so it is to be expected that someone
pi
I don't want to go into specifics because most of what I'm working on is
still high level ideas. I doubt that we'll see a separated persistence and
business logic layer land in Rails any time soon (though internally we're
actually becoming very close to that). However, we are continuing to break
