> You might want to ensure spam bots can't harvest email address of
> contributors.
We have built in stuff for that too :). They're trivially available
in git though, so there's really no avoiding it.
> Cheers,
>
> Anthony
>
>
> On Fri, Apr 3, 2009 at 5:07 AM, Xavier Noria wrote:
>> I am hap
Changed TestRequest session_options to be initialized to the
rack.session.options defaults.
https://rails.lighthouseapp.com/projects/8994/tickets/2403-testrequest-initializes-session_options-without-defaults
--~--~-~--~~~---~--~~
You received this message because
You might want to ensure spam bots can't harvest email address of contributors.
Cheers,
Anthony
On Fri, Apr 3, 2009 at 5:07 AM, Xavier Noria wrote:
> I am happy to announce that we've turned that script into a simple
> webapp that will run under contributors.rubyonrails.org or
> www.rubyonrai
On Fri, Apr 3, 2009 at 12:37 AM, Mislav Marohnić
wrote:
> This is great. I'd love for its permanent home to be
> rubyonrails.org/contributors.
> Two things:
>
> did anyone notice the long tail effect? hehe
> is the list going to be live (think github post-receive hook)
That's the idea, though t
This is great. I'd love for its permanent home to be
rubyonrails.org/contributors.
Two things:
1. did anyone notice the long tail effect? hehe
2. is the list going to be live (think github post-receive hook)
On Thu, Apr 2, 2009 at 20:37, Xavier Noria wrote:
>
> I am happy to announce th
On Apr 2, 2:56 pm, Eloy Duran wrote:
> Hi Ara,
>
> The patch looks great.
> Could you file a ticket with the same you send in this email and
> assign it to me?
>
> Thanks,
> Eloy
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2401
>
> On 2 apr 2009, at 21:51
On Apr 2, 2:56 pm, Eloy Duran wrote:
> Hi Ara,
>
> The patch looks great.
> Could you file a ticket with the same you send in this email and
> assign it to me?
>
> Thanks,
> Eloy
we crossed paths - yes i'll create a ticket too.
thanks!
>
> On 2 apr 2009, at 21:51, ara.t.howard wrote:
>
here's a correctly formatted patch, with tests
http://gist.github.com/89436
can someone give it a whack and push?
cheers.
-a
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post
Hi Ara,
The patch looks great.
Could you file a ticket with the same you send in this email and
assign it to me?
Thanks,
Eloy
On 2 apr 2009, at 21:51, ara.t.howard wrote:
>
> SYNOPSIS
> using fields_for with a nested attribute numbers the resource index
> incorrectly. although this does no
SYNOPSIS
using fields_for with a nested attribute numbers the resource index
incorrectly. although this does not cause an exception it does make
scripting js to add additional form elements harder and more error
prone than it needs to be since the form elements generated do reflect
the size of
Hi people! Perhaps you remember that effort started some months ago to
try to get a good listing of Rails contributors:
http://groups.google.com/group/rubyonrails-core/browse_thread/thread/7554c8c5a25b4765
I got plenty of feedback and kept maintaining the list in this gist:
http://gist.g
Hello,
This is the second proposal that I submitted to GSoC. Please feel free
to leave any comments on it.
Thank you.
Abstract:
Currently there is no easy way of communicating two Rails
Thanks for the Reply Allen. I'll try to add some of your suggestions
to my proposal. This is the original proposal that I submitted:
Abstract:
Currently ActiveResource requires developers to know the domain of the
REST service. The only way of knowing if a resource is available is if
the service
Hi carlosk,
I really like the idea of being able to expose an API of REST services
automatically. Can you post your proposal here?
Here are some of my suggestions for things you can think about. Some
of them may be hit or miss. I imagine you could utilize something like
rake routes to generate p
14 matches
Mail list logo
