Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Feature: Getting Started With Handling CSS #2

Open
crimson-knight opened this issue Aug 19, 2024 · 0 comments
Open

New Feature: Getting Started With Handling CSS #2

crimson-knight opened this issue Aug 19, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@crimson-knight
Copy link
Member

It's time to introduce CSS handling into the shard. There's a basic ways for handling CSS that I think that the shard should handle at least in the first iteration.

Specifically, in the beginning, we want to be able to handle CSS file similarly to how we handle group files where processing isn't happening, but we're still creating a fingerprint and caching the file. The file fingerprint is based on the files contents, and then the hash is calculated and added into the file name. This fingerprinting process helps significantly with preventing issues related to browser.

  1. The starting directory is a src-like directory for the shard to reference and iterate over find files, create fingerprint for each file, and then an output directory where the file with the fingerprinted file name will go.
  2. A file watcher process that: watches for file changes, performs the finger printing process and moving the file, then sends an update to the browser to update the source files.

Updating the browser so it doesn't require a full page refresh would make the process of front-end development a much more pleasant experience with Asset Pipeline in general.

@crimson-knight crimson-knight added the enhancement New feature or request label Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant