neocotic
neocotic
The page was created when I published v4 (Europa), but I never actually got around to writing the guide yet: https://github.com/NotNinja/europa/wiki/Migrating-from-older-versions I just want to track this so I don't...
Use a service like [Coveralls](https://coveralls.io/) to track code coverage which would be generated by the build after using something like [Istanbul](https://github.com/gotwarlost/istanbul) or [Blanket.js](http://blanketjs.org/). An initial threshold of 95% would be...
When enabled (via the options) the parser should only clean specified HTML elements (i.e. remove all of their attributes) instead of replacing them with Markdown. When "cleaning" an element, all...
For example; embedded code. Only some of these have already been done as part of #3 but I'd like to do a lot more now.
I was planning on using this in a rewrite of one of my extensions and was surprised to find it absent from npm. Could you please publish it there so...
Here's a summary of the changes that will be included in this release: - [ ] Add unit tests #5 - [ ] Adopt OOP design #12 (**breaking change**) -...
When support for JSON requests was added in 2.1.0, JSONP was kept as the default format to avoid it being a breaking change. However, since this means that credentials are...
Currently, since most consumers of this library will be using `dist/yourls.js` or `dist/yourls.min.js` this doesn't really matter as runtime dependencies are bundled with this library, but `oopsy` is under "devDependencies"....
Things to consider: * framework * libraries * env (browser vs node) * imports * coverage * mocking
Although nothing has been finalized in terms of the approach yet, this PR aims to implement a reliable unit test suite for this library in order to address #5.