Skip to content

Commit a865585

Browse files
docs: fix the harness with method's options list format in using component harnesses (#20609)
Remove whitespace that causes an item in the options list of the harness with method to be rendered as a code block.
1 parent 4d4b4da commit a865585

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

guides/using-component-harnesses.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ provided constraints. The particular constraint options vary depending on the ha
113113
harnesses support at least:
114114
115115
- `selector` - CSS selector that the component must match (in addition to its host selector, such
116-
as `[mat-button]`)
116+
as `[mat-button]`)
117117
- `ancestor` - CSS selector for a some ancestor element above the component in the DOM
118118
119119
In addition to these standard options, `MatButtonHarness` also supports
@@ -156,7 +156,7 @@ it('should mark confirmed when ok button clicked', async () => {
156156
});
157157
```
158158
159-
Note that the code above has does not call `fixture.detectChanges()`, something you commonly see in
159+
Note that the code above does not call `fixture.detectChanges()`, something you commonly see in
160160
unit tests. The CDK's component harnesses automatically invoke change detection after performing
161161
actions and before reading state. The harness also automatically waits for the fixture to be stable,
162162
which will cause the test to wait for `setTimeout`, `Promise`, etc.

0 commit comments

Comments
 (0)