Allow passing mixed to assertVue and assertVueIsNot #853
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.
This addresses the issues #845 and #850.
The
assertVue
(andassertVueIsNot
) method have a DocBlock that declared that the expected value must be of typestring
. However, Vue component data can contain data of any type that JavaScript supports. The PHPUnitassertEquals
check also supports these types.I often want to use
assertVue
to check if arrays or objects in Vue are in the desired state. So far, there are many use cases (like empty arrays, arrays with nested arrays, or objects) that are not supported yet by the available assertions in Dusk.This PR therefore allows passing
mixed
values toassertVue
andassertVueIsNot
. The error message is now set up by JSON-encoding the expected value.