Though it's less than likely a resource would return with no "id" (or only
1 attribute), I think that it needs to be considered. It's rare to find
perfect CRUD.
Imagine that User.find(123) was actually
CoolViews.find("aggregateOfAllHotTopics"). I guess that the service could
supply an "id" of
How is "Generating new project creates a few files with bad syntax Rails
3.2.1" on the wrong mailing list?
Don't confuse my reaction to the curious responses of "victims united" as
being the purpose of this thread.
I was pointing out something that I thought was a problem.
Is there a mission s
On Fri, Mar 2, 2012 at 11:36 PM, Mark Peterson wrote:
> On Friday, March 2, 2012 9:25:06 PM UTC-5, thewoo...@gmail.com wrote:
>>
>> "M" is the mute thread shortcut in gmail:
>>
>> http://support.google.com/mail/bin/answer.py?hl=en&answer=47787
>>
>> Don't feed the trolls.
>
> Yes, block your ears
On Friday, March 2, 2012 9:25:06 PM UTC-5, thewoo...@gmail.com wrote:
>
> "M" is the mute thread shortcut in gmail:
>
> http://support.google.com/mail/bin/answer.py?hl=en&answer=47787
>
> Don't feed the trolls.
>
> Yes, block your ears as users express their concerns.
--
You received this message
And I should add, though it was difficult to get myself into this fail
case, It was amazingly quick to set up 2 codebases and servers to perform
this task.
Great work people! :)
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To view
Took longer than I thought to get a basic use case that fails. Scenario 2
below is the failure:
My Code:
class User < ActiveResource::Base
self.site = "http://localhost:9000";
end
class Image < ActiveResource::Base
end
class ImagePage < ActiveResource::Base
self.element_name = "image_page"
"M" is the mute thread shortcut in gmail:
http://support.google.com/mail/bin/answer.py?hl=en&answer=47787
Don't feed the trolls.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googl
On Fri, Mar 02, 2012 at 04:47:05PM -0800, Mark Peterson wrote:
> On Friday, March 2, 2012 7:43:35 PM UTC-5, Aaron Patterson wrote:
> >
> >
> > Can you show a code example?
>
> Sure, I'll create a fresh project to juxtapose the problem this causes with
> GET and POST on the same model.
Cool, than
On Friday, March 2, 2012 7:43:35 PM UTC-5, Aaron Patterson wrote:
>
>
> Can you show a code example?
>
> --
> Aaron Patterson
> http://tenderlovemaking.com/
>
Sure, I'll create a fresh project to juxtapose the problem this causes with
GET and POST on the same model.
--
You received this mess
On Fri, Mar 02, 2012 at 04:38:06PM -0800, Mark Peterson wrote:
> On Friday, March 2, 2012 7:25:34 PM UTC-5, Aaron Patterson wrote:
> >
> > On Fri, Mar 02, 2012 at 01:26:18PM -0800, Mark Peterson wrote:
> > > So ActiveResource::Base.include_root_in_json is no longer supported, and
> > > then I enco
On Friday, March 2, 2012 7:25:34 PM UTC-5, Aaron Patterson wrote:
>
> On Fri, Mar 02, 2012 at 01:26:18PM -0800, Mark Peterson wrote:
> > So ActiveResource::Base.include_root_in_json is no longer supported, and
> > then I encounter the following within Json Formats:
> >
> > module ActiveResource
On Friday, March 2, 2012 7:19:15 PM UTC-5, Ryan Bigg wrote:
>
>
> On Friday, 2 March 2012 at 4:06 PM, Andrés Mejía wrote:
>
> I don't mean to offend, but you are one of the most annoying people to
> ever write to this list.
>
> Fire, meet gasoline.
>
> i.e. This is not the way to deal with peo
On Friday, March 2, 2012 7:09:54 PM UTC-5, eMxyzptlk wrote:
>
> lool I second that, he's like nil always whining :)
>
> Sorry dude not offending you, but clearly you woke up on the wrong side of
> the bed and decided to take it out on the most respectful list, which
> usually people don't even
On Fri, Mar 02, 2012 at 01:26:18PM -0800, Mark Peterson wrote:
> So ActiveResource::Base.include_root_in_json is no longer supported, and
> then I encounter the following within Json Formats:
>
> module ActiveResource
> module Formats
> module JsonFormat
> def decode(json)
> F
On Friday, 2 March 2012 at 4:06 PM, Andrés Mejía wrote:
> I don't mean to offend, but you are one of the most annoying people to ever
> write to this list.
Fire, meet gasoline.
i.e. This is not the way to deal with people like that. Insults will only
generate more insults. Let's not do that
On Friday, March 2, 2012 7:06:34 PM UTC-5, Andrés Mejía wrote:
>
> I don't mean to offend, but you are one of the most annoying people to
> ever write to this list.
>
>
I'm certainly not offended. Thanks!
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rai
lool I second that, he's like nil always whining :)
Sorry dude not offending you, but clearly you woke up on the wrong side of
the bed and decided to take it out on the most respectful list, which
usually people don't even use to say thanks so we do not bother the brains
behind this wonderful code
I don't mean to offend, but you are one of the most annoying people to ever
write to this list.
On Fri, Mar 2, 2012 at 6:05 PM, Mark Peterson wrote:
>
>
> On Friday, March 2, 2012 5:37:17 PM UTC-5, Mark Peterson wrote:
>>
>> On Friday, March 2, 2012 5:25:30 PM UTC-5, Prem Sichanugrist wrote:
>>>
On Friday, March 2, 2012 5:37:17 PM UTC-5, Mark Peterson wrote:
>
> On Friday, March 2, 2012 5:25:30 PM UTC-5, Prem Sichanugrist wrote:
>>
>> Oh, I put the period in the `` because the sentence ended there. Sorry if
>> that's confused you.
>>
>> The correct code is this:
>>
>> some_method(na
On Friday, March 2, 2012 5:25:30 PM UTC-5, Prem Sichanugrist wrote:
>
> Oh, I put the period in the `` because the sentence ended there. Sorry if
> that's confused you.
>
> The correct code is this:
>
> some_method(name: 'bob', age: 25)
>
> - Prem
>
Any programmer worth his salt disobeys the i
Oh, I put the period in the `` because the sentence ended there. Sorry if
that's confused you.
The correct code is this:
some_method(name: 'bob', age: 25)
- Prem
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this grou
On Friday, March 2, 2012 5:14:58 PM UTC-5, Prem Sichanugrist wrote:
>
> There's a mistyped there in the code. It has to be `name:`, not `name.`
>
I'm scared does "name." mean something? For all I know it does now :)
--
You received this message because you are subscribed to the Google Groups "R
On Friday, March 2, 2012 5:14:16 PM UTC-5, Trek wrote:
>
> >
> > Isn't "name 'bob'" the syntax for passing "bob" as an argument into the
> "name" method? Or has that all changed too?
> >
> > If I saw "name 'bob'", I would think that there's a method named "name"
> defined somewhere.
> >
> > d
There's a mistyped there in the code. It has to be `name:`, not `name.`
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
>
> Isn't "name 'bob'" the syntax for passing "bob" as an argument into the
> "name" method? Or has that all changed too?
>
> If I saw "name 'bob'", I would think that there's a method named "name"
> defined somewhere.
>
> def name(str)
> # do something with str
> end
>
>
Sounds like a great
On Friday, March 2, 2012 4:21:39 PM UTC-5, eMxyzptlk wrote:
>
> Just taking a long breath to answer you, this syntax change is not
> pointless, it's a preparation for syntax like this:
>
> some_method(name 'bob', age: 25)
>
> in some_methods, the arguments is not a *hash* but they are named params
On Friday, March 2, 2012 4:35:22 PM UTC-5, Ryan Bigg wrote:
>
>
> On Friday, 2 March 2012 at 12:15 PM, Mark Peterson wrote:
>
> You've got to be kidding? Why do these people waste their time with such
> pointless syntactical changes
>
>
> This is what would be gauged as "rage" here. They're
On Friday, March 2, 2012 4:21:39 PM UTC-5, eMxyzptlk wrote:
>
> Just taking a long breath to answer you, this syntax change is not
> pointless, it's a preparation for syntax like this:
>
> some_method(name 'bob', age: 25)
>
> in some_methods, the arguments is not a *hash* but they are named params
On Friday, 2 March 2012 at 12:15 PM, Mark Peterson wrote:
> You've got to be kidding? Why do these people waste their time with such
> pointless syntactical changes
This is what would be gauged as "rage" here. They're not *pointless* syntax
changes. They're adapting to the shorter syntax for
On Friday, March 2, 2012 4:20:50 PM UTC-5, Michael Pavling wrote:
>
> On 2 March 2012 21:18, Mark Peterson wrote:
> > Again, not sure where you got the "rage" from.
> >
>
> I tend to get it from top-posting with no trimming ;-)
>
So that's what top-posting is. Why does Google Groups default to
t
So ActiveResource::Base.include_root_in_json is no longer supported, and
then I encounter the following within Json Formats:
module ActiveResource
module Formats
module JsonFormat
def decode(json)
Formats.remove_root(ActiveSupport::JSON.decode(json))
end
end
end
en
Just taking a long breath to answer you, this syntax change is not
pointless, it's a preparation for syntax like this:
some_method(name 'bob', age: 25)
in some_methods, the arguments is not a *hash* but they are named params..
Anyway, before this becomes a flame war again, post to rubyonrails-ta
On 2 March 2012 21:18, Mark Peterson wrote:
> Again, not sure where you got the "rage" from.
>
I tend to get it from top-posting with no trimming ;-)
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to r
Again, not sure where you got the "rage" from.
On Friday, March 2, 2012 3:28:34 PM UTC-5, Prem Sichanugrist wrote:
>
> * Don't put a rage on me. I'm not the one who decide this. I explained why
> it's being that way.
> * You can generate you application with old syntax by using
> --old-style-has
Not sure where you got the "rage" from.
On Friday, March 2, 2012 3:27:12 PM UTC-5, Michael Koziarski wrote:
>
> On Saturday, 3 March 2012 at 9:15 AM, Mark Peterson wrote:
>
> You've got to be kidding? Why do these people waste their time with such
> pointless syntactical changes? Does it improve
* Don't put a rage on me. I'm not the one who decide this. I explained why it's
being that way.
* You can generate you application with old syntax by using --old-style-hash.
* That wrap_parameters thing is something else altogether. It's for when you're
calling `@model.to_json`.
- Prem
On Mar
On Saturday, 3 March 2012 at 9:15 AM, Mark Peterson wrote:
> You've got to be kidding? Why do these people waste their time with such
> pointless syntactical changes? Does it improve performance? No. Does it
> improve readability? No.
>
Same reason people waste their time writing such pointless
You've got to be kidding? Why do these people waste their time with such
pointless syntactical changes? Does it improve performance? No. Does it
improve readability? No.
Why does the comment in "wrap_parameters.rb" say the following?
# Enable parameter wrapping for JSON. You can disable this by
No, that is Ruby 1.9 hash syntax. It will generate that syntax if you're using
Ruby 1.9.
- Prem
On Mar 2, 2012, at 1:31 PM, Mark Peterson wrote:
> session_store.rb
>
> is:
> YourApplicationName::Application.config.session_store :cookie_store, key:
> '_yourapplicationname_session'
>
> should
session_store.rb
is:
YourApplicationName::Application.config.session_store :cookie_store, key:
'_yourapplicationname_session'
should be:
YourApplicationName::Application.config.session_store :cookie_store, :key
=> '_yourapplicationname_session'
wrap_parameters.rb
is:
wrap_parameters format:
I'm with Rodrigo. I really appreciate all the quality work that the Rails
core and each & every contributor puts into this awesome framework.
It made me very sad to see that Jose Valim, one of my programming idols,
was hurt by all the FUD going around. I hope he is doing well. I just wish
this
>
> I didn't find any of the posts as personal attacks or bad
> suited but perhaps is just me.
Even though I'm not as involved in contributing to Rails as 1.5 years back
but I found them very offensive. A lot of people, including you, put a lot
of hard work into Rails. And I thought they were
42 matches
Mail list logo
