-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(eslint): apply eslint fixes and remove unused codes #1044
Conversation
Test image available:
|
Test image available:
|
Test image available:
|
Test image available:
|
Seems like if the user chooses minimal deployment, the infinite effect loop error will cause the web-client to be significantly slow. Should be backport this (maybe split the fix into another PR?)? |
I wasn't able to reproduce this (backend commit: |
Opps I left out an important step: you need to launch a dev server for front-end to see react warning. Production asset won't show it. |
I tried: $ CRYOSTAT_DISABLE_SSL=true CRYOSTAT_CORS_ORIGIN=http://localhost:9000 sh run.sh in one terminal, and: $ yarn start:dev and this seems to reproduce what you're describing. If I click the notification bell to expand the drawer then I get the console errors and cannot collapse the Problem notification section. |
Okayy! Then this PR fixed it right? |
With this PR branch checked out, repeating the steps above seems to fix it - I can open and close the notification drawer as well as the Problems section, and there is no console error. |
Test image available:
|
Welcome to Cryostat! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
git commit --amend --signoff
Related to #941
Description of the change:
Chores
FC
alias forFunctionComponent
(perhaps code base can be a little bit smaller?).Fixes
run.sh
, observe the problem notification, and the browser console will show error with titleWarning: Maximum update depth exceeded.
Motivation for the change:
Regular "house-keeping" for codebase.