Skip to content

use transform#135

Merged
yoshuawuyts merged 3 commits intomasterfrom
use-transform
Jan 2, 2018
Merged

use transform#135
yoshuawuyts merged 3 commits intomasterfrom
use-transform

Conversation

@yoshuawuyts
Copy link
Contributor

Semver major. Replaces --use with --transform. Tests pass, but not sure if
package.json detection works. Did we ever get that to work? Thanks!

@codecov-io
Copy link

codecov-io commented Sep 21, 2017

Codecov Report

Merging #135 into master will increase coverage by 0.28%.
The diff coverage is 96.42%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #135      +/-   ##
==========================================
+ Coverage   97.35%   97.63%   +0.28%     
==========================================
  Files           2        2              
  Lines         151      169      +18     
==========================================
+ Hits          147      165      +18     
  Misses          4        4
Impacted Files Coverage Δ
index.js 95.45% <100%> (ø) ⬆️
transform.js 99.02% <96.15%> (+0.2%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2b5722a...78a1584. Read the comment docs.

@cjhowe-us
Copy link

cjhowe-us commented Sep 29, 2017

As I mentioned in #136, this is failing with postcss-prefix@2.1.0. I definitely don't suggest merging this, at least without changing the postcss-prefix semver! See stackcss/postcss-prefix#12

Note: I have a pull request at stackcss/postcss-prefix#13 that should fix this.

@yoshuawuyts
Copy link
Contributor Author

@cjhowe7 could you maybs give this another review? Thanks! 😁

Copy link

@cjhowe-us cjhowe-us left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woops, looks like I made a mistake on one of the tests. I'll make a PR to fix it. There's a few lines of unnecessary code I could remove too.

]
},
"dependencies": {
"sheetify": "file:../../..",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not so sure these dependencies are necessary.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed they are unnecessary. I will PR shortly to remove this.

t.equal(res, expected, 'CSS was transformed')
})

const bOpts = { browserField: false }

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably unnecessary

next()
})
})
.plugin('css-extract', { out: outFn })

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, this is definitely not supposed to be here for this test. Woops.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, wait, my bad. This is fine. I guess I confused this with sheetify-cssnext.

@yoshuawuyts
Copy link
Contributor Author

yoshuawuyts commented Oct 2, 2017 via email

@cjhowe-us
Copy link

I must have been tired when I did that review, so it should actually be working fine. If you want, I opened a pull request (#137) to remove some unnecessary options from the tests to keep them more minimal.

@yoshuawuyts
Copy link
Contributor Author

v7.0.0 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants