Aha! I hadn't thought to look on `TestCase`. Thanks!
On Sunday, March 8, 2015 at 4:37:15 PM UTC-7, Matt jones wrote:
>
>
> On Mar 6, 2015, at 12:59 AM, Brandon Weiss > wrote:
>
> Here's the method:
>
> def run_in_transaction?
> use_transactional_fixtures
Awesome! I made a pull request <https://github.com/rails/rails/pull/19282>
:)
On Tuesday, March 10, 2015 at 11:57:49 AM UTC-7, Rafael Mendonça França
wrote:
>
> Seems good to me.
>
> On Fri, Mar 6, 2015 at 4:04 AM Brandon Weiss > wrote:
>
>> I think the name
Argh, I meant if `use_transactional_fixtures` is true I get the error.
On Thursday, March 5, 2015 at 11:04:43 PM UTC-8, Brandon Weiss wrote:
>
> Here's the method:
>
> def run_in_transaction?
> use_transactional_fixtures &&
> !self.class.uses_transaction?(m
Here's the method:
def run_in_transaction?
use_transactional_fixtures &&
!self.class.uses_transaction?(method_name)
end
I'm super confused. What is `method_name`? And where does it come from?
It's not a local variable. I can find two instances of `def method_name` in
the repo and neither
I think the name "transactional fixtures" is a little misleading and
confusing, because (as far as I can tell) it doesn't really have anything
to do with fixtures.
This is pretty embarrassing, but I've been using Rails almost since 1.0 and
I had no idea that transactional fixtures were runnin
Hi guys! I'm not familiar with the acceptance policy of pull requests being
accepted into stable versions of rails.
I'm curious as to why https://github.com/rails/rails/pull/6215 is not yet
included in a release of rails despite the merge happening over 9 months
ago? Is there one last step that
I really don't see what the fuss is about. If you don't like coffee-
script then just write JavaScript. Right?
On Apr 13, 4:24 pm, Andrew Kaspick wrote:
> I prefer LESS over SASS, but I see SASS has improved since the last
> time I used it and taken some much needed pointers from LESS. I
> didn'
I will take a crack at scaffolding
https://github.com/KeysetTS/scaffolding
--
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
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2999
I've submitted a patch for this bug that raises an exception anytime
there is an Array in the request parameters with Ruby 1.9. I'd
appreciate if one of the core members could check it out and apply it.
Thank
.
I understand your desire for it to be symmetric with String#eql?, but
I think that is a separate issue. I don't feel strongly about it one
way or the other. At a minimum, #eql? and #hash should behave
properly when compared to another Chars object.
Brandon
On Mar 8, 2009, at 2:38 P
patch
incorporating the suggestion.
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1496
I'd appreciate it if someone could check it out and apply it for 2.3.
Thanks,
Brandon
--~--~-~--~~~---~--~~
You received this message because you are subsc
some other project in honor of Rails
Thanks,
Brandon
PGP.sig
Description: This is a digitally signed message part
Anything else needed to get this patch applied?
On Thu, Jan 1, 2009 at 4:08 PM, Frederick Cheung
wrote:
> Looks sane to me!
> On 31 Dec 2008, at 15:54, Brandon Keepers wrote:
>
>>
>> I've posted a patch that fixes some issues with OrderedHash doing
>> weird thin
I've posted a patch that fixes some issues with OrderedHash doing
weird things with keys. I'd appreciate it if someone could check it
out and apply it.
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1676-orderedhash-mishandles-keys
Thank
to submit it upstream :)
http://rspec.lighthouseapp.com/projects/5645/tickets/440-before-filter-are-executed-twice
Thanks Koz.
Brandon
PGP.sig
Description: This is a digitally signed message part
e path of the filename, so simply requiring application would still
re-load it.
I'm also wondering if #require_dependency is necessary in the
dispatcher. Would simply using #require do the trick?
I'm willing to pursue a patch to fix this, I just wanted to see if
anyone had
On Sat, May 31, 2008 at 1:57 PM, Brandon Keepers <[EMAIL PROTECTED]>
wrote:
> I wanted to point out a bug in Trac that was opened a couple months ago.
> When using dynamic finders on an association, the eager loading is ignored,
> which raises an error if the eagerly-loaded asso
rails. Please review and apply.
http://dev.rubyonrails.org/ticket/11562
Brandon
PGP.sig
Description: This is a digitally signed message part
I've added a patch to fix sqlite with renaming and removing columns
that have an index. Please check it out an add your +1s or suggestions.
http://dev.rubyonrails.org/ticket/10576
Thanks,
Brandon
--~--~-~--~~~---~--~~
You received this message because yo
;s to the ticket or give constructive criticism.
Thanks,
Brandon
--~--~-~--~~~---~--~~
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@goog
On Oct 23, 2007, at 11:42 AM, Josh Peek wrote:
> On Sep 30, 4:13 pm, Brandon Keepers <[EMAIL PROTECTED]> wrote:
>> I'm up for trying to tackle it if anyone wants to pitch in.
>
> Did you make any progress? Just wondering because I was going give it
> a try.
Not
On Oct 1, 2007, at 4:33 PM, Piyush Ranjan wrote:
> +1
> Totally useful
Want to add that to the ticket? ;)
> On 10/1/07, Brandon Keepers <[EMAIL PROTECTED]> wrote:
>
> http://dev.rubyonrails.org/ticket/9746
>
Brandon
--~--~-~--~~~---~--
ges. :-)
The patch also adds support for #step without a block, which will
just return an array:
(0..60).step(15) #=> [0,15,30,45,60]
Add your +1's if you think it is a worthy patch.
Thanks,
Brandon
--~--~-~--~~~---~--~~
You received this message becaus
x27;s just a
> refactoring (no API changes), then it could make 2.1.
> Otherwise, it
> can be scheduled for 3.0. Rails 2.x is not going to be the last, ever
> release of the framework ;).
Whew...that's a relief. ;-)
Brandon
--~--~-~--~~~---~--
t too late for a major change like that for 2.0?
Brandon
--~--~-~--~~~---~--~~
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
On Sep 19, 2007, at 5:13 PM, foomanchoo wrote:
>
>> The :through part of those associations is really just an
>> optimisation
>> to avoid having to write:
>>
>> @tag.taggings.map(&:post)
>>
>> If you need access to the tagging instances, just use @tag.taggings
>> instead of @tag.posts
>
> True
Could I get some reviewers for #7453? sqlite fails when trying to
modify tables without a primary key (join tables). The patch is a
simple 2 line fix with a test.
http://dev.rubyonrails.org/ticket/7453
Thanks,
Brandon
--~--~-~--~~~---~--~~
You received
On Sep 11, 2007, at 11:41 AM, Brandon Keepers wrote:
http://dev.rubyonrails.org/changeset/7315 caused some interesting
behavior with attributes marked with attr_protected. See http://
pastie.caboo.se/96099, specifically line 19. It looks like
attributes are cached and not cleared when
but I would appreciate any
pointers (koz) as I try to dig through the define_read_method, which
is where I suspect the bug is coming from.
Thanks,
Brandon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
Would the ideal solution to this be to make capture work with nested
calls?
Brandon
PGP.sig
Description: This is a digitally signed message part
epts header has "text/javascript; text/html", it would look for
rjs, then html?
Brandon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send
format
doesn't exist, I think it should use the Accepts header to determine
other template formats.
I'm looking into a patch for this.
Brandon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "R
.
In my option, it should use the order of the Accepts header to give
preference to template formats just like it does with choosing the
format for the respond_to block. What are your thoughts?
Brandon
--~--~-~--~~~---~--~~
You received this message because yo
On Jun 28, 2007, at 7:50 AM, Geoff B wrote:
> Hi, I just put in a patch that allows you to DRY up this:
>
> <%= link_to @company.name, @company %>
>
> to this:
>
> <%= link_to :name, @company %>
>
> The symbol indicates the method to be called on the object passed in
> the link_to options.
>
> h
On Dec 11, 2006, at 11:47 AM, eclaymoore wrote:
>
> Brandon,
>
> I am a Rails user in practice and do not presume to know enough to
> touch the internal code, but I am concerned by your patch to allow for
> symlinked plugins.
>
> You are suggesting to change li
would apply this patch since Rails
partially works with symlinked plugins (it loads them), but the
plugins generators and rake tasks won't work.
Thanks,
Brandon
[1] http://dev.rubyonrails.org/attachment/ticket/4245/
symlinked_plugins.patch
--~--~-~--~~~---~--~
36 matches
Mail list logo
