avo-hq/avo

Update list after "attach & attach another" action

Open

#3,434 opened on Nov 18, 2024

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Ruby (308 forks)user submission
BugHelp wanted

Repository metrics

Stars
 (1,778 stars)
PR merge metrics
 (Avg merge 1d 1h) (82 merged PRs in 30d)

Description

Describe the bug

I want only listings that are already not attached to be available for select. When I use "attach & attach another", the collection of available for select records does not update

Image

Steps to Reproduce

Steps to reproduce the behavior:

  1. Add this configuration '...'
  2. Go to '...'
  3. Click on '....'
  4. Scroll down to '....'
  5. See error

Expected behavior & Actual behavior

Models and resource files

System configuration

Avo version: 3.14.0 Rails version: 8 Ruby version: 3.2.2

License type:

  • Community
  • Pro
  • Advanced

Are you using Avo monkey patches, overriding views or view components?

  • Yes. If so, please post code samples.
  • No

Screenshots or screen recordings

Additional context

Impact

  • High impact (It makes my app un-usable.)
  • Medium impact (I'm annoyed, but I'll live.)
  • Low impact (It's really a tiny thing that I could live with.)

Urgency

  • High urgency (I can't continue development without it.)
  • Medium urgency (I found a workaround, but I'd love to have it fixed.)
  • Low urgency (It can wait. I just wanted you to know about it.)

Contributor guide

Research direction
Investigate the JavaScript code that handles the 'attach & attach another' action in the Avo admin panel. Look for the function that updates the list of available records after an attachment. The issue may be in the frontend logic that fails to refresh the list or filter out already attached items. Review the relevant view components (likely using Stimulus or similar). Also check the comments on the issue for any additional context from the assignee or maintainers.
Tech stack
ruby
Domain
full stack
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Ruby on Rails basicsAvo gem familiarityJavaScript basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60