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
{{ message }}
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
The script and link tag helpers currently just render new elements based on the result of the Matcher API and the provided globbing file paths. They should implement a more concrete ordering scheme to ensure that results and subsequently elements are always rendered in a deterministic and reliable fashion.
Proposed sort order is depth first alphabetical, e.g.:
Files:
📂 a-sub
one.js
two.js
📂 another-sub
a.js
b.js
📂 yet-another-sub
a.js
📂 b-sub
one.js
site.js
site.min.js
Globbing path: **/*.js
Resulting order:
site.js
site.min.js
a-sub/one.js
a-sub/two.js
a-sub/another-sub/a.js
a-sub/another-sub/b.js
a-sub/another-sub/yet-another-sub/a.js
b-sub/one.js
The text was updated successfully, but these errors were encountered:
The script and link tag helpers currently just render new elements based on the result of the
Matcher
API and the provided globbing file paths. They should implement a more concrete ordering scheme to ensure that results and subsequently elements are always rendered in a deterministic and reliable fashion.Proposed sort order is depth first alphabetical, e.g.:
Files:
Globbing path:
**/*.js
Resulting order:
The text was updated successfully, but these errors were encountered: