You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A while ago I created a monkeypatch for chai called dirty chai. Its purpose is to change the property assertions to method-style assertions. I have users having issues figuring out how to use it properly and would like a drop-in replacement prodatakey/dirty-chai#9.
Wonder if you guys would be amiable to an integration of the patch I do in dirty-chai directly into chai behind a configuration option.
I'd be happy to do the work, just want to see if a patch would be accepted before I work on it.
The text was updated successfully, but these errors were encountered:
If you take a look at our roadmap (#457) the plan is to eventually get to the point where chai has a range of pluggable interfaces which are generated from assertions - including a "jshint friendly" expect/should. I think this would be a better option than monkey-patching, and it'll be better for the assert style interface which doesn't get much love. Some early spitballing was made here but we need to properly bikeshed out a new declarative plugin syntax that gives enough info to interface plugins to do this kind of magic.
I'll close this one, because I think #457 shows the direction I'd rather see out of chai. If you want to discuss the ideas in #457 further, I think we should totally continue that over there.
A while ago I created a monkeypatch for chai called dirty chai. Its purpose is to change the property assertions to method-style assertions. I have users having issues figuring out how to use it properly and would like a drop-in replacement prodatakey/dirty-chai#9.
Wonder if you guys would be amiable to an integration of the patch I do in dirty-chai directly into chai behind a configuration option.
I'd be happy to do the work, just want to see if a patch would be accepted before I work on it.
The text was updated successfully, but these errors were encountered: