Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: add test with escaped characters #493

Merged
merged 1 commit into from
Apr 18, 2017

Conversation

alexander-akait
Copy link
Member

What kind of change does this PR introduce?
Tests

Did you add tests for your changes?

it is tests

If relevant, did you update the README?

not required

Summary

Ref: #459

Does this PR introduce a breaking change?

no

Other information

not required

@codecov
Copy link

codecov bot commented Apr 17, 2017

Codecov Report

Merging #493 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master    #493   +/-   ##
======================================
  Coverage    98.3%   98.3%           
======================================
  Files          10      10           
  Lines         354     354           
  Branches       79      79           
======================================
  Hits          348     348           
  Misses          6       6

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 2ee7552...094b60b. Read the comment docs.

test("escape characters (uppercase)", ".class { content: \"\\F10C\" }", [
[1, ".class { content: \"\\F10C\" }", ""]
]);
// Need uncomment after resolve https://github.com/css-modules/postcss-modules-local-by-default/issues/108
Copy link
Member

Choose a reason for hiding this comment

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

Not sure about these tbh, maybe better keep a note and add them when it is resolved :)

Copy link
Member Author

Choose a reason for hiding this comment

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

@michael-ciniawsky i think best note is not in code, some issue can resolve in a long time 😭 Be good merge this as is and if some submit about problem related to this add link to issue in other repo maybe it is help solve the problem faster

@michael-ciniawsky michael-ciniawsky changed the title Tests: add test with escaped characters. test: add test with escaped characters Apr 17, 2017
@michael-ciniawsky michael-ciniawsky self-assigned this Apr 17, 2017
@michael-ciniawsky
Copy link
Member

I will update the test suite today, so we can test within a 'real world' scenario (ETWP && style-loader)

Copy link
Member

@michael-ciniawsky michael-ciniawsky left a comment

Choose a reason for hiding this comment

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

Alright but we need to make sure, to not make css-loader a backlog of other issues 😛

@michael-ciniawsky michael-ciniawsky merged commit 6ee2fc6 into webpack-contrib:master Apr 18, 2017
@alexander-akait alexander-akait deleted the issue-459 branch April 18, 2017 10:32
@alexander-akait
Copy link
Member Author

@michael-ciniawsky If I'm not mistaken in postcss v6 we have builin value-parse maybe we can migrate to this, postcss more stable than other tools for this 😄 Now i think we can leave it at that.

@michael-ciniawsky
Copy link
Member

michael-ciniawsky commented Apr 18, 2017

Instead of css-selector-tokenizer you mean ? I wanted to try that out, but hadn't the time to do so until now, if postcss-value-parser || postcss v6 could replace it I'm all in

@alexander-akait
Copy link
Member Author

@michael-ciniawsky yep, I generally see for the first time the project using this module, we tried it in other projects, it did not meet expectations 😭 let's wait postcss v6, btw we can migrate on postcss-value-parser (or postcss-values-parser) it is more stable

@michael-ciniawsky
Copy link
Member

👍 I will open an issue for general overview with all available options here soon, so we can then triage this, but very good catch I'm surprised to be honest 😛

fahad19 added a commit to fahad19/css-loader that referenced this pull request Apr 24, 2017
* master:
  fix: case insensitivity of @import (webpack-contrib#514)
  chore: update comment (webpack-contrib#515)
  docs(README): improve importLoaders section and example (webpack-contrib#512)
  docs(README): fix link (webpack-contrib#508)
  docs(README): fix typo in example (webpack-contrib#507)
  docs(README): fix typo in maintainers link (webpack-contrib#505)
  fix: imported variables are replaced in exports if followed by a comma (webpack-contrib#504)
  docs(README): standardize (webpack-contrib#503)
  test: `charset` directive (webpack-contrib#502)
  fix: url with a trailing space is now handled correctly (webpack-contrib#494)
  fix: use `btoa` instead `Buffer` (webpack-contrib#501)
  test: add test for escaped characters (webpack-contrib#493)
  test: add tests for encoded svg data uri (webpack-contrib#492)
  test: add tests when css contain data uri and source maps are enabled (webpack-contrib#491)
  fix: loader now correctly handles `url` with space(s) (webpack-contrib#495)
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.

2 participants