avo-hq/avo

Add support for delegated types

Open

#3,162 opened on Aug 21, 2024

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Ruby (308 forks)user submission
FeatureHelp wantedStale exempt

Repository metrics

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

Description

It'd be great if avo had support for delegated type fields. I think this could work like a belongs to association?

Originally posted by @iainbeeston in https://github.com/avo-hq/avo/discussions/1356#discussioncomment-5510587

There is a closed PR about this: https://github.com/avo-hq/avo/pull/2681

Contributor guide

Research direction
Study the closed PR #2681 and the discussion in #1356 to understand the proposed implementation approach for delegated types, then implement a similar solution based on the belongs to association pattern.
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.
1-2 days
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.
Clear
Prerequisites
RubyRails
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40