I find myself needing to run a method and if the method does not exist,
have it return itself, instead of nil quite often, I think this change
could be used fairly widely.
module ActiveSupport
module Tryable #:nodoc:
def try(*a, &b)
try!(*a, &b) if a.empty? || respond_to?(a.first)
orv Parijat >wrote:
>
> For a domain, say "example.org", you would call "example.org/" as the
> "root" domain. The "root" domain points to the "home" page
> of the website. The idea of "root" should be made clear to studen
ifficult. They master the details of Rails just fine.
But I lover the fact the Rails uses a smattering of English-like DSL usage
throughout, and "root" stands out to me as something that might be improved
upon.
On Monday, 11 March 2013 12:29:02 UTC-5, Colin Law wrote:
>
> On
rough the router code and see if I can submit
a PR in time for Rails 4, and make "home" an alias for "root".
But if there's actually a good reason for keeping it as "root," let me know
and save me the effort :-)
Thanks!
Jeff
--
You received this message
a job it would be to make this change, but I'm ready
to investigate if the core team agrees that this would be something nice
for Rails 4.
Thanks!
Jeff
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To view
On Friday, 2 November 2012 10:34:19 UTC-5, DHH wrote:
>
> Jeff, I agree that the old-style validation methods are better when you do
> not need to combine options. I'm +1 for keeping them around.
>
> But the new dynamic finders are just as good as before:
>
> Product
xt? Would you put up with:
class Category < ActiveRecord::Base
associated_to :product, :ordinality => :many
end
I hope not!
So if maybe it's too late to save the validation methods, but I hope it's
not too late to save dynamic finders.
Who's with me? :-)
Thanks,
Je
e "resource" in there helps normalize our
vocabulary a bit more instead of "scaffold" which isn't really used
anywhere else in the framework.
Jeff
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
Thanks for the update! These kinds of posts are really helpful.
Jeff
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-core/-/tMQcVyye8AIJ.
Have there been any showstopping issues since rc4? It's been a couple weeks
since the last rc and I'm wondering if there are any showstopping issues I
can (if I'm lucky) help resolve. (Or is there some obvious way to know this
on Github that I'm overlooking?)
Thanks!
Je
iverecord
I added a patch to #to_s String values before sending them off to arel.
Feedback on the patch is greatly appreciated.
Thanks,
Jeff Pollard
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send
Hi guys :-)
I submitted a single-line bug fix along with two test cases on the 1
August but it hasn't received any attention yet:
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5346-rails-3000rc-bug-mysql-connection-left-in-unusable-state-after-mysqladapterselect-and-mysqlad
llation / support"
> sections:http://github.com/mislav/rails/compare/bcec0f65...doc-readmes
Overall these look really good - thanks for doing this! And the only
typo I noticed was doubled word "It it" near the beginning of the
Action Pack readme.
Jeff
--
You received this me
e the high priority stuff is mostly fixed.
+1 Me too. Maybe I've missed something obvious, but I'm not exactly
sure (from looking at lighthouse tix) what others are already working
on (don't want to duplicate effort) vs. what might be helpful to work
on (especially any docs that need upd
rity of the Rails community use
> jQuery exclusively.
Mine too.
> 2. jQuery has a vast community of its own, and a multitude of
> plugins.
> 2. Yehuda Katz.
>
I agree, and think that Rails 3 is a good opportunity to offer new
default values for a lot of things, including the default j
steps, if they’re not ready to
upgrade all the way to 3.0.
Since all of the changes are isolated to ActiveRecord/ActiveSupport,
would this be possible?
Jeff
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this g
On Feb 23, 11:18 am, Alexander Uvarov
wrote:
> On 23.02.2010, at 20:58, Jeff wrote:
>
> > On Feb 23, 12:36 am, Alexander Uvarov
> > wrote:
> >>>> 1. It maintains continuity with previous versions of rails
>
> >> You MUST rewrite your routes
r someone on the core team will agree that it
should remain as connect, or that someone from the core team will
explain why a change is necessary. I'll be happy if either of those
happen, because I will have learned something.
Jeff
--
You received this message because you are subscr
Anybody have thoughts on this one? (Criticism is ok if I'm off my
rocker.)
Jeff
On Feb 20, 2:13 pm, Jeff wrote:
> In Rails 3 routing, it seems we're using the match() method to hook up
> arbitrary url patterns to rack endpoints (which I think is a great new
> routing featur
ious versions of rails
2. It's more descriptive of the intention of a route: to connect a
requested url with an endpoint that can generate a response.
Feedback?
Thanks!
Jeff
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core"
troller::Base and modules mixed
> into ActionController::Base.
Thanks for the explanation, Yehuda. Sounds logical.
Jeff
> Yehuda Katz
> Developer | Engine Yard
> (ph) 718.877.1325
>
>
>
> On Mon, Jan 11, 2010 at 9:46 PM, Jeff wrote:
> > Hi,
>
> > I'
e code should be adopting this style, and in what situations.
Thanks,
Jeff
--
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-c...@googlegroups.com.
To unsubscribe from this group,
le
> cd railties
> rake dev
Ah! Thanks.
Jeff
--~--~-~--~~~---~--~~
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 uns
What is meant by "rake dev", by the way?
rake -T with a clean 2.3.4 app doesn't show any task named "dev" on my
box.
Jeff
On Oct 4, 2:22 pm, John Trupiano wrote:
> Hey guys, can we get this patch applied? Currently the rails app
> generated with 'rake dev
that
> > have been fixed for some time, and it would be nice to get those out
> > the door.
>
> Agreeed, 2.3.4 will be 6 weeks after 2.3.3, I'm planning to do them
> every 6 weeks from now until 3.0 ships (assuming there's
en fixed for some time, and it would be nice to get those out
the door.
You know, before 3.0 is released :-)
I don't use IRC as much as I should, so I apologize if these questions
were already answered there.
Thanks,
Jeff
-
purpleworkshops.com
softiesonrails.com
pragprog.com/titles
e error page (https://rails.lighthouseapp.com/
projects/8994/milestones/9903-2-x). Hopefully it will be fixed before
you even see this message.
Or is there a better way to look at all the tickets that should be
reviewed to see if there are any other blockers for 2.3.3?
Thanks again,
Jeff
--~--
t talking about edge rails, but just whenever there are point
releases on the horizon.
Thanks!
Jeff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send
te) is
autoflushing on every call. Which is probably fine, but unfortunately
the .flush method was removed and broke our code. Either the
signature should change to just pass one response object, or I'm
guessing the signature was preserved to try not to break old code, in
which
ne in 2.2.2.
(In our real app, we're using this technique to stream XML that's
dynamically generated from the DB because it could be a large amount
of data. If there's a better way to stream dynamically-generated data
with Metal or something like that, I'd
Can someone who has access to the http://api.rubyonrails.org/ website
regenerate the rdocs? It doesn't seem to have been updated for 2.3,
but the main www.rubyonrails.org site points there as the official api
site.
Thanks!
Jeff
--~--~-~--~~~---~--~~
You rec
The --freeze option never worked for me. I would try this:
rails --freeze myapp
and would get an error when it tried to freeze the app.
Here's a patch. I'd appreciate feedback and/or +1's.
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/174
I always forget to do "rake rails:update" after "rake
rails:freeze:gems". So I'm looking for some +1's to this simple
patch:
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1623
Thanks,
Jeff
--~--~-~--~~~---~--~-
;path/to/plugin'
> rake generate:model NAME='User' ATTRIBUTES='name:string'
>
> Regards,
>
> Ryan
I don't think rake is a good candidate for these. Ryan makes a good
point about the argument syntax being a bit awkward, but rake is built
f
dn't notice any :nodoc: labels anywhere in
the template handler classes, just a lack of RDoc-style comments. I
think explicitly using :nodoc: is a good way to indicate that it's
internal, or at least "depend on this at your own risk."
Jeff
--~--~-~--~~~-
On Dec 1, 7:07 pm, Jeff <[EMAIL PROTECTED]> wrote:
> On Dec 1, 6:57 pm, "Mislav Marohnić" <[EMAIL PROTECTED]>
> wrote:
>
> > On Tue, Dec 2, 2008 at 01:46, Jeff <[EMAIL PROTECTED]> wrote:
>
> > > /home/jcohen/sites/pw/current/vendor/rails/acti
On Dec 1, 6:57 pm, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> On Tue, Dec 2, 2008 at 01:46, Jeff <[EMAIL PROTECTED]> wrote:
>
> > /home/jcohen/sites/pw/current/vendor/rails/actionpack/lib/action_view/
> > template_handler.rb:11:in `initialize':Ar
ge from 1.8.6 to 1.8.7. I've tried switching from frozen
Rails to 2.2.2 gems but it made no difference.
Any ideas/insights/suggestions would be very welcome, this is driving
me nuts; if this is surely not a Rails bug, then I'll continue on the
rails-talk list instead.
Thanks
Jeff
--~--~--
ActiveSupport::SecureRandom.
> This simplifies the tests and code drastically, and shouldn't have
> any negative impact on security.
>
Awesome. Working fine for me so far.
Jeff
--~--~-~--~~~---~--~~
You received this message because you are sub
nyone else
besides me :-)
Thanks!
Jeff
--~--~-~--~~~---~--~~
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
then default value for
string columns, while mysql was setting a default of NULL, which broke
the inserts.
On Oct 4, 12:55 pm, Frederick Cheung <[EMAIL PROTECTED]>
wrote:
> On 4 Oct 2008, at 03:39, Jeff wrote:
>
>
>
> > I'm seeing a similar issue with mysql 5.0.51. I have a
I'm seeing a similar issue with mysql 5.0.51. I have a rails 1.2.6 app
deployed on a webhost agains mysql 5.0.27 and it works fine. however
on two different linux boxes, both running mysql 5.0.51, I get the
following error:
Mysql::Error: Column 'title' cannot be null: INSERT INTO boats
(`updated_
On Oct 1, 2:13 pm, Jeff <[EMAIL PROTECTED]> wrote:
> If this sounds good to everyone, I'll submit a patch this weekend. Not
> sure if the door is already closed on 2.2, but it would be good get
> this slipped in if possible.
...And now I see someone bea
I've changed my mind a bit... see below.
On Sep 30, 12:03 pm, Jeff <[EMAIL PROTECTED]> wrote:
> > On Sep 30, 3:43 am, "Michael Koziarski" <[EMAIL PROTECTED]> wrote:
> > > This does sound like a bug or misconfiguration somewhere along the
> >
ent-Type',
:post => 'Content-Type',
:delete => 'Accept'
}
I think the Delete request needs to send both headers, since I think
ActiveResource wants to receive the deleted content as well.
So far my attempts to send both headers are breaking existin
On Sep 30, 3:43 am, "Michael Koziarski" <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 29, 2008 at 4:38 AM, Jeff <[EMAIL PROTECTED]> wrote:
> > However, I can not delete any. Calling the .destroy method in
> > ActiveResource generates a 422 from the web
a if this is a bug in ActiveResource that I should dig into/
submit a patch for, or
is this actually by design and I'm not understanding something about
how to achieve deletes via ActiveResource?
Thanks!
Jeff
--~--~-~--~~~---~--~~
You received this message becaus
ccessible specifier necessary? In other words, are we afraid
something might break if ActiveRecord::Base#new and #create natively
understood nested hashes as well as the flat hashes that it can accept
today?
Jeff
>
> On Jul 14, 6:38 pm, David Dollar <[EMAIL PROTECTED]> wrote:
>
> &
Hello,
Apologies if I'm posting in the wrong place - I wasn't sure how else
to inform whoever is able to update api.rubyonrails.org. Seems like
it hasn't been updated for 2.1 yet?
Jeff
--~--~-~--~~~---~--~~
You received this message because you
On May 23, 11:13 am, "ara.t.howard" <[EMAIL PROTECTED]> wrote:
> On May 23, 2008, at 10:03 AM, Jan De Poorter wrote:
> it's not that simple to hack ApplicationController, at least in older
> rails.
>
Perhaps this might help? http://errtheblog.
y. There's nothing special about binary
data, there are many types that need correct conversion to/from the
database.
However, I also like your idea, because it allows lazy conversions
(which could be a win on large binary data). But the most important
#x27;s not entirely true. If you try to put invalid byte sequences
into a text field, you will get an error.
If it happens that you are not using encoding, than a sequence of
characters is (almost) equivalent to a sequence of bytes. But that is
not true for all users.
Regards,
Jeff Davis
-
On Feb 10, 9:27 pm, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> Anyone have any reasons we shouldn't do this?
>
> Well, I can think of a reason: when a user didn't have time/knowledge to
> understand a bug that he stumbled on, so he built part of the functionality
> on it (relying on the wrong
l. I've tested the patch and gave it a +1.
Jeff
--~--~-~--~~~---~--~~
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.co
ails.org/ticket/10520
>
> And while I'm writing the message here, a documentation ticket of mine
> that's pretty painless:http://dev.rubyonrails.org/ticket/10598
>
> Andrew
I posted a +1 to the doc patch. I don't feel I know eno
Existing code that relied on the current default
behavior might not work as expected anymore.
Jeff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send e
and we'll get it applied.
>
> --
> Cheers
>
> Koz
Thanks for the reply. I'll try to tackle that by the end of this
week.
Jeff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on R
course).
>
> I'd love feedback on the implementation.
I like the idea, but might suggest returning nested hashes instead. I
find them easier to work with. Is that doable? Something like:
[ 2007 => { 3=>2, 4=>2, 5=> 3 }, 2008 => { 1=>1 } ]
Just a thought.
Jeff
--~--~-
fails under 2.0.2.
Should I fix my test because this is desired new behavior? Or submit
a patch instead?
Thanks!
Jeff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to
uot; at this point:
http://dev.rubyonrails.org/ticket/10569
Thanks!
Jeff
--~--~-~--~~~---~--~~
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
future. If the core decides to wait and see before applying the
patch, that would be fine with me, too.
Jeff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to t
On Dec 19, 10:24 pm, Lawrence Pit <[EMAIL PROTECTED]> wrote:
> Hi Jeff,
>
> Sorry, don't like this.
>
> 1) Defaults should be constant imho, not variable.
I generally agree, but I think a reasonable degrade approach is
necessary here.
> 2) I'd suggest mySQL
tor to use sqlite3
if the sqlite3-ruby gem can be found. If not, the default database
will revert back to MySQL.
http://dev.rubyonrails.org/ticket/10569
+1 anybody?
Thanks!
Jeff
softiesonrails.com
--~--~-~--~~~---~--~~
You received this message because you are sub
//dev.rubyonrails.org/ticket/10565
Anyone willing to hit it with some +1s?
Thanks :-)
Jeff
--~--~-~--~~~---~--~~
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
separate...?
If not, I'd be happy to contribute a patch.
Jeff
softiesonrails.com
--~--~-~--~~~---~--~~
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 rub
writing, and get some kind of reward (monetary, recognition,
or otherwise), this is doomed to happen. It's no one's fault, it's
just how it is. Some developers are good at it (like you), most are
not. Look at the Rails blogosphere. The good ones tend to be by
developers wh
matthew deiters wrote:
> Ever need to do !object.nil? - I do and frequently. This patch is
> basically rolling up an extension i end up adding to every project i
> work on.
Um... why not just do
if object
Should be the same as !object.nil?, rig
cleanup.
But I agree, it feels funny to have to save the Post in a seemingly
invalid state up front.
Jeff
softiesonrails.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
T
are great. Ping for core to
> give it a look,
>
> Zach
Personally I prefer the current ability to specify a well-named
callback method. I think this patch would encourage large anonymous
blocks of code that would hinder refactoring, no?
Jeff
--~--~-~--~~~---~-
might. And then they will think Rails did something wrong.
My understanding from the ruby list is that 1.9 won't see the light of
day until the 2nd half of 2008, so fortunately we do have time to
figure out a solution and/or broadcast the warnings far in advance.
Jeff
--~--~-~--~~---
we did a while ago
on our blog: http://www.softiesonrails.com/search?q=rest+101
Feel free to include the link if you think it's appropriate.
Jeff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Cor
stead been packaged as gems will not
be supported in either edge or 2.0?
Keep in mind, I have no opinion one way or the other - I'm still
learning about both plugins and gems - but knowing what core will do
will influence my approach.
Thanks!
Jeff
--~--~-~--~~~-
On Aug 23, 10:02 am, Pratik <[EMAIL PROTECTED]> wrote:
> Anyone ever uses test/mocks/development && test/mocks/test directories ?
I do. Very handy sometimes.
> If someone does, test/mocks/development doesn't really seem like a
> nice place for putting development environment mocked classes. May
On Aug 15, 2:01 pm, Pratik <[EMAIL PROTECTED]> wrote:
> It's already gone :)
Yikes! I didn't notice that.
(embarrassed, backs away slowly on tip-toes)
Thanks!
Jeff
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
robably have time to submit a patch if it seems appropriate. I
do worry about backward compatibility for some folks who might be
using old components, but I say, if it's not a recommended practice,
we probably just take it out.
Thoughts?
Jeff
softiesonrails.com
--~--~-~--~~
http://dev.rubyonrails.org/ticket/8729
I ran into this same problem as the submitter did - could someone
review this ticket? Would have saved me some grief :-)
Thanks!
Jeff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
elps
people know that things really are going on behind the scenes. It
will also motivate people to get involved and help "cross things off
the list". Like at the end of a long race, turning the corner, and
now seeing the rope across finish line somehow mot
sight
into the core's current thinking about 2.0 would be really
appreciated. (David outlined new features in 2.0 at RailsConf back in
May, so are we thinking summer? fall? etc.)
Thanks!
Jeff
--~--~-~--~~~---~--~~
You received this message because you are sub
h rails does this for you now)
Thanks a lot, Koz. (And note to self: before asking, rtfm :-)
Jeff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send em
7;t have to explicitly "yield" back to keep the ball moving.
Obviously the intent here is for something more interesting - can you
say a word or two about it?
Thanks!
Jeff
(feel free to continue this on rails-talk instead, if that's more
appropriate)
--~--~-~--~~--
f most places that call themselves enterprise.
Awesome :-) I couldn't have said it better myself!
Thanks for having the courage to keep the good stuff in, and the
questionable stuff out.
Jeff
softiesonrails.com
--~--~-~--~~~---~--~~
You received this message because
do ...
> %>), with is an instance of Workshop, the form will POST to /workshops
> (or PUT to /workshops/123 if editing a saved instance).
[snip]
Thanks a lot, James - makes perfect sense now.
Jeff
--~--~-~--~~~---~--~~
You received this message becau
t; <% end %>
Can you explain this a little more? I understand polymorphics, but
still trying to grok simply_helpful, so I'm not exactly sure what
these arrays are doing in there.
(Feel free to push this thread to rubyonrails-talk if that's more
appropriate).
Thanks!
Jeff
--~--~-
#x27;t think anyone should be encouraged to take the scaffolding
views and morph them into production-quality views. I always end up
deleting most of the generated code because my projects always need
something different.
Just my two cents.
Jeff
softiesonrails.com
--~--~-~--~~-
ing the generated code. I'd hate to make them learn how to
install plugins first.
If you're instead referring to the 'scaffold' class method that can be
used in a controller, then I'm all for removing it :-)
Jeff
softiesonrails.com
--~--~-~--~~~
then it is a no brainer that plugin developers
try to use standard rails functionality before going to extensions. So I
think making it simpler to hook in (as long as it doesn't make things too
complicated or cause big performance hits, which I don
On 9/29/06, Hendy Irawan <[EMAIL PROTECTED]> wrote:
>
> Will it be considered there be an alternative extension supported for
> .rhtml files?
> Aptana and Dreamweaver doesn't support it out of the box, and I'm too
> lazy to figure out how to configure (or re-configure) them to
> recognize .rhtml f
Ooo... let us know what rules you use. ; )
-jeff
On 9/1/06, jason <[EMAIL PROTECTED]> wrote:
>
> I've turned it off for now for then because there does seem to be too
> many false positives. There isn't a way to tune it at all and it also
> doesn't seem to log a
88 matches
Mail list logo
