Skip to content

Commit

Permalink
[core] Fix react-next build
Browse files Browse the repository at this point in the history
  • Loading branch information
oliviertassinari committed May 30, 2020
1 parent 34b4602 commit ee351ea
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions scripts/react-next.diff
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,15 @@ diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/pa
index 5e83281c0..3c995f97c 100644
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -963,7 +963,7 @@ describe('<Autocomplete />', () => {
fireEvent.keyDown(textbox, { key: 'Enter' });
expect(handleChange.callCount).to.equal(1);
expect(handleChange.args[0][1]).to.equal('a');
- expect(consoleErrorMock.callCount()).to.equal(4); // strict mode renders twice
+ expect(consoleErrorMock.callCount()).to.equal(3); // strict mode renders twice

This comment has been minimized.

Copy link
@eps1lon

eps1lon May 30, 2020

Member

I think StrictMode no longer affects this. Could you assert every message and see if that's true?

This comment has been minimized.

Copy link
@oliviertassinari

oliviertassinari May 30, 2020

Author Member

Looking at it

expect(consoleErrorMock.messages()[0]).to.include(
'Material-UI: The `getOptionLabel` method of Autocomplete returned undefined instead of a string',
);
@@ -993,7 +993,7 @@ describe('<Autocomplete />', () => {
/>,
);
Expand Down

0 comments on commit ee351ea

Please sign in to comment.