Closed ai closed 9 years ago
@ai there is a linguistic contradiction: while url
is an antonym to inline
, asset
isn’t.
Renamed url
function would allow a coder to explicively state their intent to provide a path to resolve. Thus, errors instead of warnings could be shown, which also resolves https://github.com/borodean/postcss-assets/issues/8. Cases highlighted at https://github.com/borodean/postcss-assets/issues/8#issuecomment-72524903 wouldn’t throw warnings anymore.
The problem is how to pick a proper new name. It should be as simple as possible, yet clear. It should also be semantially similar with inline
. asset
doesn’t work here, because it gives no clue about what it does. It is also not highlighting it's principal opposition to the inline
one.
@ai, what do you think about calling it resolve
?
Other idea is asset-url
as in Rails. resolve
looks like nice too (and shorter).
Maybe we should use special semantic
asset()
function instead of commonurl()
?