Skip to content

Commit

Permalink
Prepare for 3.0.2 release
Browse files Browse the repository at this point in the history
  • Loading branch information
joshgaber committed Oct 8, 2022
1 parent 791e59d commit 491da28
Show file tree
Hide file tree
Showing 4 changed files with 15 additions and 2 deletions.
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,14 @@

All notable changes to NovaUnit will be documented in this file.

## 3.0.2

- Allow `FieldElement` as a valid field instance

## 3.0.1

- Use built-in `NovaRequest` for mocking components

## 3.0

- Compatibility with Laravel Nova 4
Expand Down
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,8 @@ If you discover any security related issues, please email joshgaber@gmail.com in

* [Joshua Lauwrich Nandy](https://github.com/joshua060198)
* [nicko170](https://github.com/nicko170)
* [Henry Ávila](https://github.com/henryavila)
* [Peter Elmered](https://github.com/pelmered)

## License

Expand Down
2 changes: 1 addition & 1 deletion composer.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "joshgaber/novaunit",
"description": "Unit testing suite for Laravel Nova, built to extend PHPUnit",
"version": "3.0.1",
"version": "3.0.2",
"keywords": [
"laravel",
"nova",
Expand Down
5 changes: 4 additions & 1 deletion docs/fields.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,10 @@ Asserts that the `fields()` method returns an empty array.
$component->assertHasValidFields();
```

Asserts that all fields returned by the `fields()` method are valid Nova Fields.
Asserts that all fields returned by the `fields()` method are valid. Examples of valid fields include:
* `Field` instances
* `FieldElement` instances
* `Panel` instances (including any nested objects)

## Testing Fields Individually

Expand Down

0 comments on commit 491da28

Please sign in to comment.