Bump @storybook/addons from 7.4.0 to 7.4.1 in /generators/app/templates #3087
Triggered via pull request
September 13, 2023 19:03
dependabot[bot]
Status
Success
Total duration
6m 42s
Artifacts
–
Annotations
16 warnings
|
app-tests-JwtDtoWebsocketsAppV6
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “NavContainer” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
|
app-tests-JwtDtoWebsocketsAppV6
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component and pass data as props
|
|
app-tests-JwtDtoWebsocketsAppV6
'fireEvent' is defined but never used
|
|
app-tests-JwtDtoWebsocketsAppV6
["onSubmitEditing"] is better written in dot notation
|
|
app-tests-JwtDtoWebsocketsApp
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “NavContainer” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
|
app-tests-JwtDtoWebsocketsApp
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component and pass data as props
|
|
app-tests-JwtDtoWebsocketsApp
'fireEvent' is defined but never used
|
|
app-tests-JwtDtoWebsocketsApp
["onSubmitEditing"] is better written in dot notation
|
|
app-tests-OauthHealthPointsApp
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “NavContainer” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
|
app-tests-OauthHealthPointsApp
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component and pass data as props
|
|
app-tests-OauthHealthPointsApp
'fireEvent' is defined but never used
|
|
app-tests-OauthHealthPointsApp
["onSubmitEditing"] is better written in dot notation
|
|
app-tests-OauthFlickrApp
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “NavContainer” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
|
app-tests-OauthFlickrApp
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component and pass data as props
|
|
app-tests-OauthFlickrApp
'fireEvent' is defined but never used
|
|
app-tests-OauthFlickrApp
["onSubmitEditing"] is better written in dot notation
|