avo-hq/avo

Enable a field to be displayes as another field on a different view

Open

#2,315 opened on Jan 3, 2024

View on GitHub
 (3 comments) (2 reactions) (0 assignees)Ruby (308 forks)user submission
DSL-relatedEnhancementHelp wanted

Repository metrics

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

Description

Feature

It's common to use two fields to display the same data in different views.

Example:

  field :status, as: :select, show_on: :forms, ...options
  field :status, as: :badge,  hide_on: :forms, ...options

Maybe there's an API to make this available without duplicating the fields.

Current workarounds

Using two fields.

Contributor guide

Research direction
Explore Avo's field API to understand how fields are registered and rendered on different views. Investigate if there is already a mechanism to alias fields or customize field display per view. Propose a simple API that allows specifying an alternative field representation for a different view without duplicating field definitions.
Tech stack
ruby
Domain
backend
Issue type
Feature
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.
Half day
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
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60