Roadmap

This repo now has few more maintainers (including myself).

Before making any big changes would like to:

Say Hi

hi

Make a todo list

1. Rewrite tests and use real browsers to run them: https://github.com/eligrey/classList.js/pull/69
2. Fix https://github.com/eligrey/classList.js/issues/48
3. Publish a new version
4. Close my fork https://github.com/yola/classlist-polyfill/issues/9
5. Cleanup whitespace
6. Minify via npm prepublish
7. Start addressing open issues

Flesh out any preferences, paint a bikeshed

When writing JS I generally stick to airbnb-ish style.

For testing, prefer Mocha+chai (with karma running the tests) instead of QUnit.

Prefer plain old shell or JS scripts instead task managers.

[euwest]

@stevenvachon:

another preference is for single-purpose pull requests.

I agree … about #53. IMO it does too much at once.

That’s @beck responding to:

I fixed #48 in the “Consolidated closures” commit in #53. I fixed whitespace in the “Whitespace fixes” commit in #53. I rewrote the tests in the “Improve tests” commit in #53.

He’s telling you he would like those to be separate PRs, not just separate commits. Condescension is not an appropriate response.

[stevenvachon]

He’s telling you he would like those to be separate PRs, not just separate commits. Condescension is not an appropriate response.

And I’m telling him and anyone else that they can go through the commits. I have little interest in redoing my PRs after all this time.