Yeah, we definitely could never make this change. It'd be too major of a
backwards incompatible change.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I do not think we would consider this proposal without a stronger reason as to
why it is causing harm. It would be an unnecessary breaking change to existing
apps.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from
Yes, a redesign is currently being worked on.
On Saturday, December 20, 2014 12:50:35 AM UTC-7, Anandu B Ajith wrote:
The site is having a very old design and not usable ..
shouldn't we switch to a better design in 2015??
--
You received this message because you are subscribed to the Google
This is not currently public API, the final API will likely support default
values when it is made public in the future.
On Tuesday, December 23, 2014 2:19:14 AM UTC-7, Benji wrote:
[Braindump]
I stumbled on the code to define an attribute in the model. Since my
personal opinion is that
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
