Conversation
…mpatibility issue with CRA
… UserService.test.ts
ui/src/pages/Login/Login.tsx
Outdated
| const login = mutation.mutateAsync; | ||
|
|
||
| useEffect(() => { | ||
| if (isSuccess) { |
There was a problem hiding this comment.
Could it be done still with onSuccess option, but passed to usePostUserLogin hook?
There was a problem hiding this comment.
Ok, fixed as proposed
| import { userService } from "services"; | ||
| import { FormikInput, FeedbackButton } from "components"; | ||
| import { useMutation } from "react-query"; | ||
| import { usePostUserChangepassword } from "../../../api/apiComponents"; |
There was a problem hiding this comment.
api can be also a named path like contexts or services
There was a problem hiding this comment.
Already fixed
|
@katekozlowska the tests seem to be failing |
ui/package.json
Outdated
| "@types/react-router-dom": "^5.3.3", | ||
| "@types/yup": "^0.32.0", | ||
| "axios": "^1.6.5", | ||
| "axios": "0.27.2", |
There was a problem hiding this comment.
@katekozlowska so we're still using a downgraded axios?
There was a problem hiding this comment.
axios has been removed
ui/package.json
Outdated
| "eslint-config-prettier": "^9.1.0", | ||
| "formik": "^2.4.5", | ||
| "immer": "^10.0.3", | ||
| "openapicmd": "^2.4.0", |
There was a problem hiding this comment.
is this the openapi generator that we are using? the docs in stack.md mention openapi-codegen, is that still used?
There was a problem hiding this comment.
not needed anymore. Removed it
ui/package.json
Outdated
| "react-router-dom": "^6.21.1", | ||
| "react-scripts": "^5.0.1", | ||
| "typescript": "5.1.6", | ||
| "typescript": "4.9.5", |
There was a problem hiding this comment.
is the TS downgrade necessary?
There was a problem hiding this comment.
Upgraded to latest
| @@ -0,0 +1,321 @@ | |||
| /** | |||
| * Generated by @openapi-codegen | |||
There was a problem hiding this comment.
if this is generated, should it be checked in to VCS?
| @@ -0,0 +1,4 @@ | |||
| # THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY. | |||
There was a problem hiding this comment.
The yarn.lock file is added to a frontend project to ensure consistent dependency versions across all environments where the project is installed. It locks the specific versions of dependencies and their sub-dependencies, preventing potential issues caused by version mismatches. Including it in the repository ensures that all team members and deployment environments use the exact same dependency tree, improving reliability and avoiding unexpected bugs.
There was a problem hiding this comment.
yeah, but this one is in the top-level directory, shouldn't we have a non-empty ui/yarn.lock?
|
nice job @katekozlowska 👏 |
This information has been added to the |
Fixed, not showing anymore |
No description provided.