Update include assertion docs for object properties #610
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Originally added in chaijs#230, asserting that an object contains a subset of properties and values was never documented. Questions like chaijs#193 have popped up asking for this feature even though it's been present since 1.9.0. The discussion in chaijs#193 focused mostly around getting something like this to work via the `property` assertion, but that discussion should be considered moot by the existing functionality already present in `include` that was simply overlooked. Resolves: chaijs#193
keithamus
added a commit
that referenced
this pull request
Feb 8, 2016
Update include assertion docs for object properties
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Originally added in #230, asserting that an object contains a subset of properties and values was never documented. Questions like #193 have popped up asking for this feature even though it's been present since 1.9.0.
The discussion in #193 focused mostly around getting something like this to work via the
propertyassertion, but that discussion should be considered moot by the existing functionality already present inincludethat was simply overlooked.