The Drupal Asset system (Drupal\Core\Asset) is unable to serve file outside of the app/webroot. It is primarily designed to serve out of web accessible/module/extension directories.
With Pinto, some distribution strategies may in effect place assets in odd places, such as vendor.
The Asset system is capable of serving files via stream wrappers. E.g you can serve library assets out of private:// public:// etc with theme definitions like:
mylibrary:
css:
layout:
public://styles.css: {}
Provide a stream wrapper that can serve CSS & JS assets for Pinto objects.
Effectively, an artificial URL will map to a specific single asset entry from ObjectListInterface::assets(). So a combination of: asset type (JS / CSS), enum, enum case, asset.
A routable URL needs to be provided by the stream wrapper at \Drupal\Core\StreamWrapper\StreamWrapperInterface::getExternalUrl that returns a world accessible way to get the asset. This, I believe, is only necessary when CSS/JS asset preprocess is off. Otherwise assets will all be resolved internally then squashed together when preprocess is on.
Active
0.3
Code
