-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feat/#2123 upgrade dependencies client #2173
Conversation
…ly fixes to codebase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed this is a big one! This is almost all good to me.
I noticed a few bugs and added some comments in the PR.
I agree that we should use the next router for the backoffice. This was the plan but still not done because we could not find the time for it
@@ -84,7 +84,7 @@ const UserContributions = (props: Props) => { | |||
); | |||
} | |||
window.scrollTo(0, 0); | |||
}, [dispatch]); | |||
}, [dispatch, userStructure]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that this one is causing an infinite loop which fetch data all the time (this is probably more a bug in the code of the effect)
You can experience it by going in the backoffice, in the "Fiches" tab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't reproduce this 🤔 I checked the Network tab in developer tools and it just get's the data once (twice because running in dev mode actually)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok maybe something wrong with my local db. Let's try it on staging then!
@@ -56,7 +56,7 @@ export const UserStructureComponent = (props: Props) => { | |||
); | |||
} | |||
window.scrollTo(0, 0); | |||
}, [dispatch]); | |||
}, [dispatch, userStructure]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like for the userContributions, this is causing an infinite loop.
You can see it by going to the Structure tab of the backoffice (you need to be a user with a structure for this)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again I can't reproduce this locally.
…o @testing-library/react
…pWithProvidersAndRenderForTesting
…les. Update .scss imports
…pening aliased scss paths in vscode
…pescript-plugin-css-modules
Sorry this is a big PR. Was originally going to split up into separate PRs but combined to get dependency upgrade done and move on to other work. Commits take this step by step and are a good source of information on the issues involved.
styledcomponents
upgrade and update codebase by typing calls tostyled.div
and updating all test snapshots. Noticestyledcomponents
v6 no longer supports vendor prefixes by default since no longer required in modern browsersRemaining Major Dependency Upgrades: