You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a way to transform resources either at runtime (dev environment) or at startup or at build time (and then the framework doesn't care).
We could offer a pipeline API which would associate a resource to its built equivalent and map it to one single path. And then would transform it or not dependeing on the context.
Example
If we're on a dev environment :
When the user asks for assets/*.css, look for web/styles/*.scss, then send invoke my transform function and return the result.
If we're on a production environment :
Look for every file in web/styles/*.scss, if you fin their equivalent into dist/styles/*.css then it's OK, serve directly those files when assets/*.css is asked. If some are missing, please invoke my transformation function and save the result.
Pretty complicated to explain, not that easy to implement, but very useful.
The text was updated successfully, but these errors were encountered:
What is a pipeline ?
It's a way to transform resources either at runtime (dev environment) or at startup or at build time (and then the framework doesn't care).
We could offer a pipeline API which would associate a resource to its built equivalent and map it to one single path. And then would transform it or not dependeing on the context.
Example
Pretty complicated to explain, not that easy to implement, but very useful.
The text was updated successfully, but these errors were encountered: