Skip to content

Breaking: Rename .deep.property to .nested.property#757

Merged
lucasfcosta merged 2 commits intochaijs:masterfrom
meeber:nested-property
Aug 14, 2016
Merged

Breaking: Rename .deep.property to .nested.property#757
lucasfcosta merged 2 commits intochaijs:masterfrom
meeber:nested-property

Conversation

@meeber
Copy link
Contributor

@meeber meeber commented Jul 26, 2016

  • Previously, the deep flag had unexpected behavior when used with the
    property assertion: Instead of switching from strict to deep equality,
    it unlocked the ability to use dot and bracket notation when referencing
    property names. This behavior now belongs to the new nested flag.
  • assert.deepProperty renamed to assert.nestedProperty
  • assert.notDeepProperty renamed to assert.notNestedProperty
  • assert.deepPropertyVal renamed to assert.nestedPropertyVal
  • assert.notDeepPropertyVal renamed to assert.notNestedPropertyVal

Note:

meeber added 2 commits July 24, 2016 19:52
- Previously, `expect(obj).not.property(name, val)` would throw an Error
if `obj` didn't have a property named `name`. This change causes the
assertion to pass instead.
- assert.propertyNotVal renamed to assert.notPropertyVal
- assert.deepPropertyNotVal renamed to assert.notDeepPropertyVal
- Previously, the `deep` flag had unexpected behavior when used with the
`property` assertion: Instead of switching from strict to deep equality,
it unlocked the ability to use dot and bracket notation when referencing
property names. This behavior now belongs to the new `nested` flag.
- assert.deepProperty renamed to assert.nestedProperty
- assert.notDeepProperty renamed to assert.notNestedProperty
- assert.deepPropertyVal renamed to assert.nestedPropertyVal
- assert.notDeepPropertyVal renamed to assert.notNestedPropertyVal
@keithamus
Copy link
Member

keithamus commented Aug 1, 2016

LGTM 👍. @lucasfcosta?

@lucasfcosta
Copy link
Member

Awesome job regarding the docs. Very clear instructions. 👍
Code LGTM too. But read this before merging.

Regarding this one I have the same doubt as I've had here.
Shouldn't breaking changes be merged to 4.x.x first instead of master?

@lucasfcosta lucasfcosta merged commit d4e8a4a into chaijs:master Aug 14, 2016
@meeber meeber deleted the nested-property branch August 6, 2017 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants