similar to: warning: toplevel constant SomeController referenced by Admin::SomeController

I have an odd problem. I got controllers in a namespace and controllers outside of the namespace. For example, I have a PagesController and a Admin::PagesController. When I run rspec from the top, tests pass and I get the following warning: spec/controllers/admin/pages_controller_spec.rb:4: warning: toplevel constant PagesController referenced by Admin::PagesController This makes no sense. I do

In Ruby, classes are never closed: you can always add methods to an existing class. This applies to the classes you write as well as the standard, built-in classes. All you have to do is open up a class definition for an existing class, and the new contents you specify will be added to whatever''s there. In the same regard, if module is used with the name of a pre-existing module that

Hello! Are the plans of splitting ActionPack for several gems (AbstractController, ActionView, etc)? Like https://github.com/rails/rails/pull/7356 ... I.e. I know gems that are needed AbstractController only... And they are forced to require the whole ActionPack... Thanx. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To

For example, you see files called rails/actionpack/lib/action_controller/base.rb which adds methods and such to the open module ActionController. What scope is ActionController in? Is it just called the global scope? Obviously, there is namespace resolution lookup. And a good example of this is in the Base class of the same file. It references one module like this: AbstractController::Layouts

Code sample: class SomeController < ApplicationController before_filter do |c| add_crumb "Blah", "/blah" #breadcrumbs plugin redirect_to :controller => "foo", :action => "bar" unless c.send (:has_package?) end # Rest of the controller... private def has_package? # A bunch of logic work to check to make sure # somebody''s session contains

I just upgraded to Rails 1.1 and have now gotten a few of these to stdout: /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.0/lib/action_controller/routing.rb:249: warning: toplevel constant Type referenced by Item::Type What do they mean? Joe -- Posted via http://www.ruby-forum.com/.

Working on Rails Engine. I want to make the controllers customizable whereever the Rails Engine is used. Therefore, I was trying to use `extend ActiveSupport::Concern` on the Engine controller class and include it in MyRailsApp. https://gist.github.com/4185823 # code in my rails engine moduel MyEngine class SomeController extend ActiveSupport::Concern def engine_some_method

I''m building a users web service (direct dispatching) that will (I hope) allow several other applications to manage the same pool of users. Plus it will act as a single-sign-on solution for what I''m doing. But I''m having difficulty accessing the UserAPI. Here''s what I''ve done so far: $> rails usermanagement - "usermanagement" is the

I''m heading out of town, but had a quick thought I wanted to share. Rather then using ambiguous named request helpers in controller specs like "do_request", I''ve been using more readable helpers like "post_create". For example... describe ProjectController do def post_create post :create, ... end before do end it "creates a new

hi all, I want to move some routing tasks out of the router and into the controller. The goal is to make Merb feel less like mod_rewrite and give the user more control at the controller. The new Router is simple: it takes the path_info (not the whole request) then outputs a controller class and some parameters from the path matching. The rest of the routing would be done at the controller level.

Out of curiosity, I''ve seen the following fail: module Admin describe MyController ... end end But this works fine: describe Admin::MyController .. end Why? Scott

Hi, I''ve done AJAX calls to Rails'' Controllers before yet never required to generate a response back to the view. In this respect, I have tried to keep it moronically simple and just add a node to see that it works, yet the response doesn''t come through / isn''t interpreted as it should. Long story short, code : // Have to use Mootools to integrate a

What would be the best way to create a form select dropdown box and upon "submit" have it directly go to a controller method view? I have something that somewhat works, but I think there is probably a much easier way to do it. As of now, I have the dropdown list which when the form is submitted is handed to a controller method which basically I have my dropdown box: <%=

Hi, I''ll appreciate insight on this one... it''s causing me some pain on my production env. <%= link_to "something", :controller => "somecontroller", :action => ''someaction'', :id => someid, :favorite => is_a_favorite %> I added a boolean :favorite to the URL arguments. THis has always worked well under my dev

Can anyone explain where render() comes from in ActionController::Base? I managed to trace it down only that far: ActionController::Base includes ActionController::Rendering where render() method is defined. This definition however calls to render of the superclass. Superclass is ActionController::Metal. Which in its turn inherits from AbstractController::Base. None of those have render () either

Hi When building with GCC 10, gcc is stricter in handling handling of symbol clashes. Fedora, has fixed this with a patch from Dominik Mierzejewski: https://src.fedoraproject.org/rpms/tftp/c/5e2aa55b6802a52ef480d688b3ae4751220f20e0.patch Attaching the corresponding patch for git am. Regards, Salvatore >From 9e7641bf58df9dda3bc51f381f371fa7cbce47af Mon Sep 17 00:00:00 2001 From: Salvatore

Hi When building with GCC 10, gcc is stricter in handling handling of symbol clashes. Fedora, has fixed this with a patch from Dominik Mierzejewski: https://src.fedoraproject.org/rpms/tftp/c/5e2aa55b6802a52ef480d688b3ae4751220f20e0.patch Attaching the corresponding patch for git am. I'm sending the patch which was submitted a while ago to the list. Is there something you wanted to be

In trfs-progs 4.4 the error message has been changed, and our check did not work anymore. Yes, parsing user messages really sucks... --- daemon/btrfs.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index 85dbe00..c67af83 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@ -1029,9 +1029,12 @@ do_btrfs_subvolume_show (const char

Hi everybody, I am trying to write a simple progress display based on a tcltk toplevel. My first approach was to use the progressBar widget from the BWidget library but since this is not available on every system (missing on at least almost all windows systems, I guess...) I wanted to have a backup there. So my second strategy was to use a simple toplevel with a label and update the tclvariable

> I agree, impact of issue is limited. But it prevents out of the box > compilation of libraries for some targets. > Also, looks like glibc and eglibc maintainers do not welcome patches > for llvm (yet). I would be very surprised if glibc ever does. I don't have any experience with eglibc. > In general, saving order of appearance doesn't seem to be bad thing. > Are