Hello,
http://rails.lighthouseapp.com/projects/8994/tickets/515-make-plugin-generator-create-rails-init-rb
This patch is another step in the effort of having single code-base
for GemPlugins and classic plugins. This will ease migration from
plugins to GemPlugins.
There are also few tickets rega
Count me in. Recently I submitted two patches in the same area:
http://rails.lighthouseapp.com/projects/8994/tickets/515-make-plugin-generator-create-rails-init-rb#ticket-515-1
http://rails.lighthouseapp.com/projects/8994/tickets/272-make-plugins-also-initialize-form-rails-init-rb#ticket-272-1
A
> Or make Rails look for it in either place in plugins, and only have it
> in rails/init.rb for gems. I thought this was already the case, but
> maybe it was just discussed and not implemented yet.
It's the case - it was not implemented, but I had a spare moment so I
created a patch:
http://rai
> One reason would be to provide some namespacing of the init hook for
> gems that work with multiple frameworks, or have a purpose outside the
> context of Rails.
Is init.rb in the main gem directory ever used by gems infrastucture?
I couldn't find any reference of that but I agree - it's more
a
It happens again - I've commented under
http://rails.lighthouseapp.com/projects/8994/tickets/122-rails-init-rb-doesn-t-get-called-for-unpacked-gems
and it's marked as spam...
I'm starting to think about changing my profession and become a famous
spammer :)
On May 10, 12:13 p
Hello,
Why do we have to put "rails/init.rb" into a gem and not simply
"init.rb" in main dir of a gem to make it behave like a plugin? Are
there some special reasons for that?
It would be cool to have one codebase which can be packaged as a gem
or used as a classic plugin.
On the other hand, so
Thanks a lot,
Jacek
On May 10, 1:39 pm, Michael Koziarski <[EMAIL PROTECTED]> wrote:
> I've marked your stuff as ham, rick tells me that should whitelist you.
>
> Cheers
>
> Koz
>
> On 9/05/2008, at 10:49 AM, Jacek Becela <[EMAIL PROTECTED]> wrote:
>
&
Hello,
Every ticket I create in Rails LH gets incorrectly flagged as spam.
What should I do? Is there anyone scanning through spams to unmark
these? Anyone else has the same problem or is it only me?
Here's an example:
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/153
Rega
On Mar 1, 7:49 pm, Jacek Becela <[EMAIL PROTECTED]> wrote:
> Hello,
>
> http://dev.rubyonrails.org/ticket/9742
>
> If anyone is annoyed by that, please find a moment to review the
> patch. It's rather tiny and tested enough. It still applies cleanly
> (r8
Hello,
I've just added a patch to http://dev.rubyonrails.org/ticket/9742
which should (tests pass) work as advertised in the subject line.
This is my first contribution, please take a look. Feedback greatly
appreciated.
--
Jacek B
On Nov 27, 10:16 am, Nicola Piccinini <[EMAIL PROTECTED]> wrote:
> I believe that SETUP_NEEDED should be considered in conjunction with
> immediate mode, I've added a second "proof of concept" patch to the
> ticket.
>
> By the way, there could be a problem with theopen_id_authentication
> plugin
Hello,
This should interest anyone using open_id_authentication plugin. There
is a bug in current version which causes that
authenticate_with_open_id method doesn't yield the result but silently
returns when server returns with OpenID::SETUP_NEEDED response.
This patch ( http://dev.rubyonrails.o
Yup, somehow didn't stumble upon that.
On 12 Lis, 13:35, Tarmo Tänav <[EMAIL PROTECTED]> wrote:
> Isn't thishttp://dev.rubyonrails.org/ticket/9051?
>
> On E, 2007-11-12 at 12:14 +, Jacek Becela wrote:
>
> > Hello,
>
> > In User model:
> >
Hello,
In User model:
has_many :projects, :through => :authorizations
In view:
render :partial => @user.projects
This blows up because HasManyThroughAssociation inherits from
AssociationProxy and not AssociationCollection.
Partial logic checks if @user.projects === AssociationCollection wh
Thanks for quick reply.
--
Jacek
On Oct 17, 10:08 pm, "Jeremy Kemper" <[EMAIL PROTECTED]> wrote:
> On 10/17/07, Jacek Becela <[EMAIL PROTECTED]> wrote:
>
> > Below is a test case which shows strange fixtures behaviour (tested
> > against edge revision 79
se!"
Topic.find(2).update_attributes(:content => content)
assert_equal content, topics(:second).content # passes
end
end
--
Jacek Becela
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on R
16 matches
Mail list logo
