embracing proxies

Hi,

We could start enjoying the power of proxies to create even better DSL. Examples:

let element = { visible: true }
element.should.be.visible

let element = { isVisible: true }
element.should.be.visible

let response = { status: 200 }
response.should.have.status(200)

WDYT?

[meeber]

My first impression is that it sounds cool in theory but in practice it opens the door too wide for mistakes and unexpected behavior without adding enough benefit over .property(name, value). As discussed in #726, one of our central focuses is making it difficult for developers to accidentally write tests that look and act as if they’re correct but actually silently aren’t.

I think enabling cool shortcuts like .be.visible is better served via domain-specific plugins as opposed to enabled via a proxy-based catch-all.

[meeber]

@yairper I suspect it’s possible to write a normal plugin (http://chaijs.com/guide/plugins/) that implements the desired behavior by replacing be and have with custom logic. Adding chai-plugin keyword to the plugin’s package.json would cause it to be added to the website list.

If it turns out there’s really no way to implement this behavior through the plugin system and forking Chai is the only option, then I’m not sure what the best way to advertise it is. @keithamus @lucasfcosta?