Skip to content

Conversation

@westonganger
Copy link
Owner

Why:

  • Sprockets v4 manifest file has all sorts of rough edges with rails engines
  • Exposing the engines assets publicly can give away details about things that should be internal only
  • We can easily avoid it altogether and just load the assets as part of the application layout
  • There are such minimal amount of asset code that there really is no benefit to any HTTP caching

@westonganger westonganger force-pushed the remove_assets_pipeline_usage branch 2 times, most recently from 2741ecd to df17fb6 Compare January 18, 2025 03:18
@westonganger westonganger force-pushed the remove_assets_pipeline_usage branch from df17fb6 to 417f343 Compare January 18, 2025 03:26
@westonganger westonganger merged commit c4dedf7 into master Jan 18, 2025
13 checks passed
@westonganger westonganger deleted the remove_assets_pipeline_usage branch January 18, 2025 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants