Hey Everyone! Has anyone seen issues with page reloads not happening after a save or an action? If I edit a record and click save the page just sits there. But if I go back to the resource manually the save has been completed. Looking at the console, there are 2 requests, a post to the resource endpoint that ends as 302, and then a get call. I'm assuming that there is some JS that should then load the results of the get request, but I'm having trouble tracking down whats happening. Thanks for any help!

what version of Avo are you using?

Right now

gem "avo", "~> 1.8"

I'll try updating to see if it helps 🙂

Same result on

avo (1.11.6)

can you please log an issue on Github describing this? I'll try to reproduce and fix asap

Yep, thank you!

I found the issue when making a sample app to reproduce. Apparently I was loading the wrong rails defaults after a rails upgrade from a while ago. I guess there is a big difference between

config.load_defaults 6.0

and

config.load_defaults 6.1

Thanks for being so ready to jump on the problem!

is it possible to add

name

to fields such as

has_many

, e.g.

field :goal_templates, as: :has_and_belongs_to_many, name: "Goal templates"

such that it can affect the displayed name for the relationship? or, is there another way to handle this? thanks!

has_many

naming bug

good morning. is there a quick example of how to modify resolve_find_scope for a resource without using the friendly gem?

Of course @cool-greece-65430. Check out the docs here https://docs.avohq.io/1.0/customization.html#custom-find-scope

You’ll find snippets of what to do to add the friendly gem

Thanks but I asked about an example that doesn’t use a gem. I don’t want to add another dependency for something that should be doable without one

oh, got it

you'd probably still want to use that block

resolve_find_scope

to do that

I don't have any snippets or examples for that I'm afraid

raised this little issue around deleting attachments through active storage - https://github.com/avo-hq/avo/issues/487

would have sent a PR but wanted to check how this is intended to work in case i've got things setup incorrectly

thanks. yeah I know that using that block is the thing to do, I just don't understand how I use it to define how to find the model. It should be easy in theory but the underlying machinations aren't straightforward and neither is that friendly gem. Unfortunately I'm leaning towards not using avo at all as a result.

hey - hope you don't mind me jumping in to try help... the

resolve_find_scope

helper provides the model's class directly. so if you want to make sure the find scope only includes users which have not been deleted you'd do something like:

ruby
class UserResource < Avo::BaseResource
  self.resolve_find_scope = ->(model_class:) do
      # model_class here is User so to do something like:
      # User.where(deleted_at: nil)
      model_class.where(deleted_at: nil)
  end
end

it's a scope here - so what would get run would be

User.where(deleted_at: nil).find(whatever_id)

avo will handle calling the

find

method so you don't need to add that in the

resolve_find_scope

yes. perfect explanation here👆

model_class.where(deleted_at: nil)

is the qeuvalent of

User.where(deleted_at: nil)

Hello Everyone. Thanks for building Avo. I am facing a problem regarding custom field. I have generated a field like this...

bin/rails generate avo:field custom_text

then tried to use it for a string column...

field :name, as: :custom_text

But it doesn't work. The field just disappears from view. Can anyone help?

My Ruby: 2.7.2 Rails: 6.1.3.2 Opened an issue: https://github.com/avo-hq/avo/issues/495

I responded on the issue page 👆

@lemon-wall-20836 Thanks a lot. I tried restarting the server. It didn't help. I tested the feature in another dummy project and linked the PR in the issue. Please have a look when u have time. Thanks again.