Core" group.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-core+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
Szymon
>
> --
> 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/-/FSdTDr6g6CwJ.
> To post to this group, send email
groups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
>
--
Piotr Sarnacki
http://piotrsarnacki.com
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post t
oogle Groups
> "Ruby on Rails: Core" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/rubyonrails-core/-/5DmvGbSVkYwJ.
>
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> To unsubscribe from this group, send email to
>
to readability, it's much
better to say params[:slug] or params[:name] if that's what it is.
I would like to have the ability to set the name of that param. Anyone from
core team cares enough to accept/reject this idea?
--
Piotr Sarnacki
http://piotrsarnacki.com
--
You received this mes
group, send email to
> rubyonrails-core@googlegroups.**com
> .
> To unsubscribe from this group, send email to
> rubyonrails-core+unsubscribe@**googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/**
> group/rubyonrails-core?hl=en<http
and you can choose any library you want to render
JSON with rails. If you need this kind of feature, you should rather talk
with maintainers of one of the JSON libraries out there.
--
Piotr Sarnacki
http://piotrsarnacki.com
--
You received this message because you are subscribed to the Google Group
an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
P
is group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Piotr Sarnacki
http://piotrsarnacki.com
--
You received this message
On Oct 18, 7:13 pm, Joe Fiorini wrote:
> ActionDispatch::Assertions::RoutingAssertions (https://gist.github.com/
> a57e3addfe0aa3857e12). Does anyone else see value for this in core? Is
> the code okay?
I personally would not use that. You're just adding line to tests that
ensures that you adde
I don't think that you need to do such unit tests, without mounting an
engine you will not be able to reach engine's routes, so tests will
fail anyway.
> Yeah i have spent the last week trying to mount an app
Remember that this is still an edge version and some things can (and
probably will) chan
Damn, google groups ate my post, so again ;)
Joe Fiorini:
I don't like that kind of tests. You just add a line in tests that
ensures that you added a line in routes. Better way to do that would
be to check if engine can be properly rendered inside application. But
I'm not in core and it's only my
I think that Lunks is right, it's something with your config:
http://pastie.org/1370927
On Dec 12, 6:38 pm, Lunks wrote:
> You might wanna check if you have a partial rails install from your OS (i.e.
> apt). Try removing everything and then installing the rails gem strictly
> through rubygems.
>
Hey,
Indeed, I started work on that, mainly because of mountable
applications (engines), but it can be used to generate any kind of
rails extension. It's based on http://github.com/josevalim/enginex and
the key difference in comparison to older plugins generator is that
dummy application is genera
+1 from me on that. I also added my comment.
On Jan 11, 10:11 am, Nick Sutterer wrote:
> Aaron- thanks! I added comments to answer your questions.
>
> On 10 Jan., 23:50, Aaron Patterson wrote:
>
>
>
>
>
>
>
> > On Mon, Jan 10, 2011 at 01:32:11PM -0800, Nick Sutterer wrote:
> > > Hey friends,
>
>
I like Nick's implementation, not everyone know or remembers that
modyfing object like Hash or Array will also change the superclass
(which is clearly visible in the commit that Nick's linked - that was
exactly the reason of the bug that I was fixing).
I think that it would be nice to have inherit
he solution on this..
>
> Thanks
>
> --
> 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
I totally agree with what Josh said. When I used staging rails environment
in the past it always ended up with some weird tweaks that I had to do. If
you're running staging server on production environment all you need to do
is to remember to keep configuration outside the code as Josh mentioned
Please specify which plugin have you used for engines migrations in 2.3 or
describe your situation better - how does your migration files look like?
On Wednesday, May 2, 2012 11:18:29 AM UTC-7, Vanuan wrote:
>
> As I discovered on github https://github.com/rails/rails/issues/5424
> rails engines
to your app they should
be skipped on next migrations:install task.
>
> On Thursday, 3 May 2012 05:59:56 UTC+3, Piotr Sarnacki wrote:
>>
>> Please specify which plugin have you used for engines migrations in 2.3
>> or describe your situation better - how does your migration fi
To view this discussion on the web visit
> https://groups.google.com/d/msg/rubyonrails-core/-/aULxrpmyo5IJ.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-core+unsubscr...@googlegroups.com.
> For mor
On Fri, May 4, 2012 at 11:24 PM, Scott Johnson <7.scot...@gmail.com> wrote:
> So my questions for the group are, does this seem like a reasonable
> solution or am I missing something like, this is why ActionController::Base
> exists and why don't you just open class it in the load path for the sam
ail to
> rubyonrails-core+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core&q
ick reply...
>
> I have not used isolate_namespace concept...
>
> controller also not loaded like models...
>
> cau u plz tell me any other solution
>
> On May 28, 3:34 pm, Piotr Sarnacki wrote:
> > Short answer is: namespace your models, for example you should ha
gt;> .
>>> >
>>> > --
>>> > 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 .
byonrails-core@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-core+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
>
--
Piotr Sarnacki
http://piotrsarnacki.com
--
You rec
> "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
> rubyonrails-core+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/gro
27 matches
Mail list logo
