avo-hq/avo

Unavatar field

Open

#2,994 opened on Jul 16, 2024

View on GitHub
 (5 comments) (1 reaction) (1 assignee)Ruby (308 forks)user submission
FeatureGood first issueHelp wanted

Repository metrics

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

Description

Feature

Unavatar.io is a seriously cool service. I coould see a field that would use it's API to display cool avatars.

# possible API
field :username, as: :unavatar

field :username, as: :unavatar, fallback: "https://source.boringavatars.com/marble/120/1337_user?colors=264653r,2a9d8f,e9c46a,f4a261,e76f51"

field :domain, as: :unavatar

field :username, as: :unavatar do
  # record.github_profile == "https://github.com/adrianthedev"
  record.github_profile.split('/').last
end

field :username, as: :unavatar, provider: :github

Contributor guide

Research direction
Explore the unavatar.io API to understand its endpoints and response format. Then look at Avo's existing field implementations, such as Gravatar or other custom fields, to see how fields are structured. Implement a new field type that calls unavatar.io and returns the avatar URL. Consider adding configuration options for fallback, provider, or block.
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.
2
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
Ruby on RailsAvo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70