Not support resource class that placed in module

[Ivanov-Anton]

For example we have class Main::User
I want to perform search my users via ajax but I got error:

Cannot auto detect resource to fetch options for searchable select input from

[tf]

A possible solution should be suggested as part of the error message, i.e. explicitly specifying the options endpoint resource. Or is this is this a different problem?

[Ivanov-Anton]

Main::Order have relation named :invoice, class_name: 'Main::Invoice' this is belongs_to type so
In ActiveAdmn page of order I define filter :invoice, as: :searchable_select, ajax: true
in ActiveAdmin page of Invoice I define searchable_select_options scope: Main::Invoice.all, text_attribute: :name

Finaly I expect to render Order page and searchable select is work

but I got error: undefined method all_options_admin_main_invoices_path' for #<#Class:0x00007fce8737f4a8:0x00007fce8737cfc8>`

[Ivanov-Anton]

I have all_options_admin_invoices_path route instead

[Ivanov-Anton]

If I set config named resource got another error:
filter :invoice, as: :searchable_select, ajax: { resource: 'Main::Invoice' }

undefined method all_options_admin_Main::Invoice_path' for #<#<Class:0x00007f8ce4375eb0>:0x00007f8ce4360498>

[Ivanov-Anton]

So looks like this gem do not support Namespaced Classes

[tf]

Try passing the resource without quotes: filter :invoice, as: :searchable_select, ajax: { resource: Main::Invoice }

[tf]

How does the ActiveAdmin.register call for invoices look like?

[Ivanov-Anton]

How does the ActiveAdmin.register call for invoices look like?

ActiveAdmin.register Main::Invoice, as: 'Invoice' do

[Ivanov-Anton]

Try passing the resource without quotes: filter :invoice, as: :searchable_select, ajax: { resource: Main::Invoice }

filter :invoice, as: :searchable_select, ajax: { resource: Main::Invoice }

result error: undefined method all_options_admin_main_invoices_path' for #<#<Class:0x00007fa21b0aeac8>:0x00007fa21b09ead8> Did you mean? all_options_admin_invoices_path

[tf]

That's exactly the same setup I use in one of our engines. There it works without a problem. Not sure what the difference is. Maybe you can spot it?

https://github.com/codevise/pageflow/blob/fedf751ba8abb79d593d76f328db60359350c560/admins/pageflow/entry.rb#L60-L63

https://github.com/codevise/pageflow/blob/fedf751ba8abb79d593d76f328db60359350c560/admins/pageflow/accounts.rb#L43-L48

[Ivanov-Anton]

The difference is that the model class does not lie inside the namespace

[Ivanov-Anton]

In your case belongs_to :account, counter_cache: true
in my case belongs_to :invoice, class_name: 'Main::Invoice', foreign_key: :invoice_id

[tf]

It does. Pageflow::Entry/Pageflow::Account. The whole file is wrapped in module Pageflow. What might be the difference is that Pageflow is an engine. Main is only a module I guess.

Can you try filter :invoice, as: :searchable_select, ajax: { resource: 'invoice' }.

[tf]

Sorry. I meant: filter :invoice, as: :searchable_select, ajax: { resource: 'invoices' }. Plural.

[Ivanov-Anton]

Sorry. I meant: filter :invoice, as: :searchable_select, ajax: { resource: 'invoices' }. Plural.

undefined method `name' for "invoices":String excluded from capture: No host specified, no public_key specified, no project_id specified