Skip to content

Explain why we use trim when reading test file contents #12

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

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions test/index.spec.js
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,11 @@ describe('babel-plugin-css-modules-transform', () => {
}

function readExpected(path) {
// We trim the contents of the file so that we don't have
// to deal with newline issues, since some text editors
// automatically inserts them. It's easier to do this than to
// configure the editors to avoid inserting newlines for these
// particular files.
return readFileSync(resolve(__dirname, path), 'utf8').trim();
}

Expand Down