Conversation
|
@material-ui/core: parsed: +0.08% , gzip: +0.06% |
|
For fixing the error - https://app.circleci.com/pipelines/github/mui-org/material-ui/37282/workflows/f4054c2a-44af-4550-8ada-1e1c75514d81/jobs/220749 I believe we need to introduce a new option to the |
|
Alright I have taken a shot at getting |
Did you try to introduce some |
|
Oh I see what you mean. |
Exactlly, just watch out that the return result from render is a bit different, I suppose you would need to alter the |
|
Ok let me know what you think of 370b4c5 Maybe once we get this figured out I should wait till it gets merged to next, then rebase next for the |
Exactly what I had in mind, I would maybe just suggest renaming the param to |
I was just wondering the same thing as I re-read my comment Ill wait to hear the instructions. Ill Start on a none table component until we get this merged into next |
| return wrapper.find('table').childAt(0); | ||
| }, | ||
|
|
||
| wrapRender: (node) => { |
There was a problem hiding this comment.
Agree with Marija, render sounds better and more consistent with what Sebastian did with mount.
| wrapRender: (node) => { | |
| render: (node) => { |
There was a problem hiding this comment.
Am I still ok to use wrapRender in the conformance tests as the name would conflict with the normal render?
| return wrapper.find('table').childAt(0); | ||
| }, | ||
|
|
||
| wrapRender: (node) => { |
There was a problem hiding this comment.
Marking this for future follow-up: check-out something like render(node, { container: document.createElement('tabl') }) (need to check for connectedness and cleanup)
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
|
I suck at rebasing... Ill open a new PR |
#24405