Upgrade assetgraph to version 4.11.0 #160
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've upgraded a dependency and all tests pass. \o/
You should probably take a good look at this before merging this pull request, of course.
What changed?
✳️ assetgraph ( → 4.11.0) · Repo
Commits
See the full diff on Github. The new version differs by 51 commits:
4.11.0
Merge branch 'feature/es6ifyFontCode'
Merge pull request #874 from assetgraph/feature/traceCustomCssProperties
Disable the prefer-template eslint rule in lib/util/fonts/counterRendererByListStyleType.js
eslint --fix .
eslint: Enable the prefer-template rule
Reindent snippets in comments
post{C => c}ssValuesParser
es6ify font processing code
Trace the complete font-family value, and don't unquote it
Inject the subset font family into custom properties that contribute to font or font-family properties and contain the name of the original font
Use initialValueByProp in the subsetFonts transform
normalizeFontWeight: Strip +bolder... before looking up the value in css-font-weight-names
Simplify font-weight handling in expandTransitions
Use normalizeFontWeight when expanding animations and transitions
Normalize font weights in subsetFonts
Delay the normalization of font-weight
initialValueByProp: Add initial value for font-stretch
Don't break when expanding custom properties that lead to impossible predicate combinations
Forward prop when expanding custom properties
Also extract font-style from the font shorthand
Merge the normalization of font-family and font-weight
Fix tracing of font-family and font-weight through the font shorthand property
Add another pending test for the font shorthand
Add pending tests for the font shorthand property
Delay Number-ification of font-weight values
Test custom property expansion in counter-increment
Test custom properties combined with the content property
Add skipped test of animating a custom property used for font-weight
Prevent infinite recursion when there's circular custom property definitions
Expand custom properties after animations so they can be combined
Move the custom property expansion code to a separate file
Fix predicates of the "custom property not found" hypothetical value
Implement tracing and expansion of custom properties
eslint --fix .
Update prettier to ~1.13.5
Use 1-based line and column numbers when warning about missing glyphs
subsetFonts: Mention the font-weight and font-style when warning about missing glyphs
Merge pull request #879 from assetgraph/depfu/update/npm/eslint-5.0.0
Upgrade eslint to version 5.0.0
Merge pull request #877 from assetgraph/depfu/update/npm/read-pkg-up-4.0.0
Upgrade read-pkg-up to version 4.0.0
Merge pull request #876 from assetgraph/depfu/update/npm/sift-6.0.0
Upgrade sift to version 6.0.0
Use array spread instead of concat
Fix unused parameter
Support multiple hypothetical counter-increment values for the same counter
Merge pull request #875 from assetgraph/depfu/update/npm/sinon-6.0.0
Upgrade sinon to version 6.0.0
Use array spread instead of Array.prototype.push.apply(...)
source-map: Explicitly stay on 0.6.x (before the webassembly rewrite and all the breaking changes)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.