Hello fellow engineers, do you happen to know if there is a way to display a banner, warning, modal or red square, or actually any form of visual indication, in the edit view of a record when that record has a specific attribute set to true?

Is there a way to increase the number of results when searching? I'm searching for a name of a record, but as there are quite a few, the one i'm after doesn't get returned.

how to hide edit button for has_one association ? example: user.rb has_one :book has_one :library, through: :book in user_policy def edit_library? false end doesnt work it seems that it only checks edit? in LibraryPolicy

Hey , is it available to show errors messages during attach assocation ? example: user.rb has_many :teams has_many :friends, through: :teams in avo resource field :friends, as: :has_many, through: :teams if admin went to user page and click on attach friend and some error happend ( ActiveRecord::RecordInvalid) i want to be able to view the eror message as an admin , but nothing is shown

Hey i found an error while trying to create a related association , i've this models event has_many :teams, dependent: :destroy has_many :players, through: :teams team belongs_to :event has_many :players, dependent: :destroy player belongs_to :team has_one :event, through: :team` now when i try to create a player from event page the url has this

via_relation=events

when i click save player is saved, however there is an error in redirection in this method

def after_create_path
      # If this is an associated record return to the association show page
      if is_associated_record?
        parent_resource = if params[:via_resource_class].present?
          Avo.resource_manager.get_resource(params[:via_resource_class])
        else
          Avo.resource_manager.get_resource_by_model_class(params[:via_relation_class])
        end

        association_name = BaseResource.valid_association_name(@record, params[:via_relation])

        return resource_view_path(
          record: @record.send(association_name),
          resource: parent_resource,
          resource_id: params[:via_record_id]
        )
      end

as

association_name

returns nil , because` params[:via_relation]` is events but the association to the player is actually event

Hi! I'm having a "weird" issue with the reordering feature. I'm using act_as_list 1.2.1 and Avo 3.9.1 and locally it works fine, but on production it's doing something interesting where it doesn't seem to update the records affected. I'm showing the position number in the index table, so I end up for example with two position 10 or three position 11, is it cache related? https://cdn.discordapp.com/attachments/1141725701549072486/1261054704637706301/Screenshot_2024-07-11_at_3.20.34_PM.png?ex=66919036&is=66903eb6&hm=35f7e749e871ea28d2de8a752391f4f00db46e2d0ea3c2080507dbc494b3b14c&

Hey all - we're trying to check a permission within a resource#display_fields method, and want to know if the pundit policy is available in this context, and if so, how would we access it?

Is there any easy way when using modules and the self.class_name argument for a resource to override the name that appears in the ago application sidebar?

Bit of an odd one: I have my two models: Attraction belongs_to :venue Venue has_many :attractions This is great and Avo is managing them excellently. I use

friendly_id

and have set the index query to:

self.find_record_method = -> {
        if id.is_a?(Array)
            query.where(slug: id)
        else
            query.friendly.find id
        end
    }

This too works great. Each record has it's slug and in my app, the slug of an Attraction contains the name and another attribute of the Venue it is associated with. I have it all configured so that if the

name

or

location_1

values of the Venue get changed, then the slugs of the Attractions get updated too. I know slugs don't typically change but it is very useful in my case. If I make a change to a Venue that causes a new slug to be generated and I came from a standard Resource Index view (eg: http://localhost:3000/avo/resources/venues/drayton-manor-drayton-bassett) and edit it, it's fine, but if I get to the edit page and I have a URL like (http://localhost:3000/avo/resources/venues/drayton-manor-drayton-bassett?via_record_id=accelerator-drayton-manor-drayton-bassett&via_resource_class=Avo%3A%3AResources%3A%3AAttraction) When it tries to go back to the page in the

via_record_id

query param, it fails, because the slug is no different and the record can't be found. It all makes sense and I understand why it's occuring. My question is, what do you think? Are there any options to overcome this? Can you think of other ways to deal with this? I am considering adding a new field altogether which sort of replicates the nromal

slug

field but always stays in sync with the name, venue and location_1 values and just let the regular

slug

column act like that and once set, never change. Would that make more sense?

Any idea why I keep getting Unpermitted Parameter errors? How should I permit them? Unpermitted parameters: :location_1, :location_2, :location_3, :country, :coordinates, :sort_letter, :notes, :website_url. Context: { controller: Avo::VenuesController, action: create, request: #, params: {"authenticity_token"=>"[FILTERED]", "venue"=>{"order_visited"=>"", "name"=>"sdd", "type"=>"theme_amusement_park", "slogan"=>"", "mascot"=>"", "location_1"=>"1", "location_2"=>"2", "location_3"=>"3", "country"=>"AF", "coordinates"=>{"lat"=>"1", "lng"=>"1"}, "sort_letter"=>"", "notes"=>"", "website_url"=>""}, "button"=>"", "controller"=>"avo/venues", "action"=>"create"} }

Hey all, on resources its possible to define

default_sort_column

, but is it also possible to change the default sort order to asc (it defaults to descending otherwise)?

personal opinion: I think the

record_selector = false

should be set by default instead of true, since there's no need to show the select field unless you have an action that does something to the selected records; which in 99% of the cases, no one has

Folks, how would you have a "Filter" but with a different type of the

field

that you need to display on the Index view? For example: I have a field as

badge

, but my filter for this field needs to be as :select. Any ideas on how I could have this config?

Does anyone have an example of a custom select field with autocomplete search capabilities? Maybe I could use a lib instead of writing my own with stimulus?

Since there are many Card classes that we want to use generically, is it possible to set the id as an argument? Avo 3.13.6, even if the id is specified within the query as shown below, the id becomes nil, causing an error. Up until Avo3.13.1, it was possible to set the id as an argument as shown below.

class Avo::Cards::SumTotalNumber < Avo::Cards::PartialCard
  self.partial = 'avo/cards/sum_total_number'

  def query
    self.id = arguments[:id]
    ...
  end
end

def cards
    card Avo::Cards::SumTotalNumber, cols: 1, rows: 2,
         arguments: { id: :foobar, foo_data:, bar_statistics:...
  ...

is it possible to have resource name in uppercase? for example "NOC codes" instead of "Noc codes"

Thread automatically created by rctneil in #1141725701549072486

Hi, This is not a complaint or concern, merely a question: I have models of Attraction, Company, Companyable. The associations are: Attraction:

has_many :companyables, as: :companyable
    has_many :companies, -> { distinct }, through: :companyables

Company:

has_many :companyables
    has_many :attractions, through: :companyables, source: :companyable, source_type: 'Attraction'
    has_many :roles, -> { distinct }, through: :companyables

Companyable:

belongs_to :company
    belongs_to :companyable, polymorphic: true
    belongs_to :role, optional: true
    belongs_to :model, optional: true
    belongs_to :submodel, optional: true

This works fine and on my Attraction resource I have:

tab "Companies" do
                field :companyables, as: :has_many
            end

This works fine and allows me to add new companyables via the UI where I can select the Role, the Model, and the SubModel for it. This all makes sense to me, but looking at it from a User perspective, they have no idea what a "Companyable" is, it's a made up word that means absolutely nothing to them. To them they "want to add a Company to an Attraction", but technically what they need to do is "Add a Companyable to an Attraction" as the Companyable holds all the info about the role and the model/submodel. Do I leave everything as it is and try to explain to Users what it means or can you recommend changes that may make it more user friendly and user understandable? Changes could be as simple as altering wording. Could I change "Companyable" to "Company" just in the context of the UI? If I did that then the sidebar item for "Companyables" would be confusing. It's tricky. Technically it all works beautifully and i'm very happy with it. Right now I ahve no plans to roll this out to other people so it is a non issue but it is something i've been thinking of how I could overcome it if I was to roll it out to others in the future.

Thread automatically created by rctneil in #1141725701549072486

Hi there. Wondering if someone could help here? I'm getting the following error:

NoMethodError in Avo::Venues#index
Showing /home/vscode/.local/share/mise/installs/ruby/3.3.5/lib/ruby/gems/3.3.0/gems/avo-3.25.0/app/views/avo/base/index.html.erb where line #2 raised:

undefined method 'avo_pro' for an instance of #<Class:0x0000ffff7206cee0>

All I added was the following in order to enable record reordering:

self.ordering = {
    visible_on: :index,
    actions: {
      higher: -> { record.move_higher },
      lower: -> { record.move_lower },
      to_top: -> { record.move_to_top },
      to_bottom: -> { record.move_to_bottom },
    }
  }

Thread automatically created by rctneil in #1141725701549072486

Hey y'all Been trying to get Avo to work with remote HTTP resources. Tried ActiveResource, failed miserably. Then, found those docs for Avo 4 https://docs.avohq.io/4.0/http-resources.html I understand that it's still in alpha and the timeframe to Avo 4 might not be as clear. STILL It looks like HTTP resources are only available for fancier licenses like Pro or Advanced. Is it gonna be the case after the release? If so, what kind of license would that require?

Hi everyone, how are you? How can I configure an AVO resource to just have show and index views, without allowing deletion, edition, or creation? And more importantly, where is this in the docs? I was unable to find it.

Hi everyone, Does anyone know if it's possible to disable a link to another resource on the index page? On this image, people often click on one of the blogs intead of clicking on 1. https://cdn.discordapp.com/attachments/1141725701549072486/1436002489257164800/image.png?ex=697582c9&is=69743149&hm=763163543d175d593a7bd5f6ffdca1ee5e4dd11661ba48378a96c62ec82895ac&

G'day folks. I've got a question about cards. As far as I can tell, on the show pages, the location of cards is limited to the top of the page. Is there any way to move this position elsewhere, like say below the main panel or in a different panel altogether? It would be nice to do something like this for instance:

main_panel do
  field ...
  field ...
  field ...
end

panel do
  card ...
  card ...
  card ...
end

So I can position cards in specific places rather than be limited to the cards across the top of a page?

I guess I can use resource tools to do some of this since I'm using using partials

Hi, I've got a resource that has a :photos field. This is a has_many association. My Photo record does indeed have an image AS attachment, and the title field is basically the uploaded files name (not very useful) But my field definition has

searchable: true

, when I click to choose Photos, the resulting UI, either a standard select box or the searchable custom UI, are neither very useful due to this being a more visual record type. Ideally, we could have a UI similar to the media browser, but showing Photo records and using a specific field on the Photo record as the thing to display (eg, the file attachment).

CRUD, Callbacks and Actions I have a general question about how to handle, say, "side-effects". For example, in our application, a user has absences (e.g. a vacation from day x to day y). There is a lot of calculation going on in the background about how many days are needed for this timeframe, as there might be public holidays, and the employee might not work on fridays, etc. So when changing the start and end date of the absence, I need to recalculate stuff, create some dependent records, etc. When writing the controller myself, I would either do this in the controller, together with the

absence.update

, or just call some kind of "Service" all together, which handles the update and all side effects. However, with Avo, I'm not writing the controller myself - and as far as I can tell from the documentation, I can only set some redirect paths and similar in the controllers. One way to solve this would be callbacks in my model, a

before_update :update_absence_days

. This works, however, I generally try to avoid callbacks, as they are hard to reason about, especially in large applications, and they make testing harder, especially when creating records with FactoryBot Another way I found are actions, where I can mimic the editable fields and then do all of my logic inside the

def handle

method. That works well, and I can disable the regular edit with authorization. However, it is rather verbose to add an action for each of the modifying CRUD operations (to be fair, I currently only need these side effects for very few ressources, but that might change). Are there any other ways to handle these kinds of side effects that I'm missing? Did you maybe think about this topic and came to something like a "suggested solution"? Thanks for any input! 🙂

Multi-Select filters (dynamic and standard) I want to add filters for my users index view. I can single-select filter by e.g.

role

, that works fine. Now I want to extend this to multi select: 1. With the Standard filters, I can manually select multiple entries by CMD+click. However, only ~4 entries are shown, but my list is a lot longer - the filter is missing a scrollbar! And besides that, the UX could be improved to something like the tags-field (I know, multi selects are really hard, been there, done that...) 2. I tried out dynamic filters, but could only filter for one role, not for multiple. Any chances or plans to add this? Could be a good reason for upgrading my subscription 😉

Basic Select Filters I got two issues with the basic select filters. First one is just a documentation issue - on [this page](https://docs.avohq.io/4.0/basic-filters.html#show-a-message-when-there-are-no-options), it states that

self.empty_message

is shown when there are no options. But actually, it is simply used in the template as

include_blank: filter.class.empty_message || "—"

. So it can be used to overwrite the default unselected value with e.g. "All" or to remove the empty option all together. Might be even easier to just call this

self.include_blank

😅 The other one is also about the empty option. When e.g. browsing the [Avo demo posts resource](https://main.avodemo.com/avo/resources/posts), there is a basic select filter for the published state. Selecting published posts works, and then switching back to "–" shows all posts again. However, switching on persistence with

config.persistence = { driver: :session }

in the

avo.rb

breaks this behaviour. Now switching back to "–" will always switch back to the last chosen option (e.g. published). When adding a

debugger

to the

def apply

for this filter, it shows that the value only ever comes in as "published", but never as empty string, nil, or similar, so this happens before this method. I didn't look into the code here, but probably it just checks if an option is selected and if not, applies the last filter state from the persistent memory. So this probably needs some kind of check whether the empty option was picked on purpose or if it is the initial page visit for that resource...