You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following warning appears in the console while running the application: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
This warning points to the LoadingIndicator component here (and exists in other components as well), which currently relies on defaultProps for setting default values. As this feature will be deprecated in upcoming React versions, the codebase should transition to using default parameter values in function component definitions.
Steps to reproduce
Run the application using the default settings.
Navigate to the link to the UI in browser
Observe the console for the warning.
Expected behavior
The defaultProps should be removed from the codebase and migration should be done similar to this as discussed previously on Slack
Relevant log output
Support fordefaultProps will be removed from function componentsin a future major release. Use JavaScript default parameters instead.
Screenshot
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
The text was updated successfully, but these errors were encountered:
What happened?
The following warning appears in the console while running the application:
Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
This warning points to the
LoadingIndicator
component here (and exists in other components as well), which currently relies ondefaultProps
for setting default values. As this feature will be deprecated in upcoming React versions, the codebase should transition to using default parameter values in function component definitions.Steps to reproduce
Expected behavior
The defaultProps should be removed from the codebase and migration should be done similar to this as discussed previously on Slack
Relevant log output
Screenshot
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
The text was updated successfully, but these errors were encountered: