Andri Möll

Stumbled upon this problem too here in Estonia.

Hey, Samuel! Thanks for the PR! I think I set my time machine in the wrong direction and missed one year. :D Seems this is a related to https://github.com/moll/js-must/issues/21. One...

Hey! I think your contribution is still worth looking at and I expect to do so. Thank you again! I'll keep this open, if you don't mind, as a reminder...

Hey! Thanks for sharing your thoughts! I've had that need occasionally myself, too, and have had an idea to add a `Must.prototype.props` that internally uses the same equality algorithm that...

That's true, but in this case wouldn't you say making it customizeable would make it more convoluted for the reader? The `Must.prototype.properties` matcher is, after all, equivalent to the 3...

I'll do `props` for sure, but coming back to testing your responses, have you thought of just doing `body.must.eql({a: 1, b: 2})`? Where do the other properties come from that...

Yep, my controller responses differ from the database or model instances too — that's why I mentioned the`serialize` function. If, however, the controller adds properties above and beyond the functional...

Hey, @verkholantsev! Really long time no speak! ^_^ I asked something in https://github.com/moll/js-must/issues/11 that I'd like to get your opinion on, too. I'll quote it here to make your life...

Hey! Sure, customizing what gets stringified makes sense. I see there's `Must.prototype.throw` that uses the `actual` parameter for assigning to the error object but still expecting the original `actual` (the...

Hey! Thanks for taking the time to let me know about this and sorry about the trouble! I'm guessing it could be an issue with trying to serialize the DOM...