avo-hq/avo

Version Avo assets

Open

#2,147 opened on Dec 18, 2023

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Ruby (308 forks)user submission
Help wanted

Repository metrics

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

Description

Users have asked to have the Avo-produced assets versioned so they will be busted on every deploy just like Rails'

Maybe the initial iteration would be to add Avo's version number to them.

Also look into how to compile them inside the builds directory when the user configures the new TailwindCSS integration. That would make it more in line to how Rails does it.

Contributor guide

Research direction
Investigate how Rails handles asset versioning (e.g., asset pipeline helpers like asset path with fingerprints). Explore how Avo currently loads its assets and where they are built. Check the Avo build system for TailwindCSS integration to see how to compile assets into the builds directory.
Tech stack
rubyrails
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.
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.
Clear
Prerequisites
RubyRailsGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70