Updates changelog markdown

This commit is contained in:
Mihovil Ilakovac 2023-06-26 14:30:55 +02:00
parent 4a8842f296
commit 60e7c76afd

View File

@ -4,12 +4,12 @@
### Breaking changes
- Wasp's **signup action** `import signup from '@wasp/auth/signup` now accepts only the user entity fields relevant to the auth process (e.g. `username` and `password`).
This ensures no unexpected data can be inserted into the database during signup, but it also means you can't any more set any user entity fields via signup action (e.g. `age` or `address`).
Instead, those should be set in the separate step after signup, or via a custom signup action of your own.
- This ensures no unexpected data can be inserted into the database during signup, but it also means you can't any more set any user entity fields via signup action (e.g. `age` or `address`).
- Instead, those should be set in the separate step after signup, or via a custom signup action of your own.
- Wasp now uses **React 18**! Check the following upgrade guide for details: https://react.dev/blog/2022/03/08/react-18-upgrade-guide .
The most obvious difference you might notice is that your `useEffect` hooks run twice on component mount.
This is due to the React 18's StrictMode, and it happens only during development, so it doesn't change the behaviour of your app in production.
For more details on StrictMode, check https://react.dev/reference/react/StrictMode .
- The most obvious difference you might notice is that your `useEffect` hooks run twice on component mount.
- This is due to the React 18's StrictMode, and it happens only during development, so it doesn't change the behaviour of your app in production.
- For more details on StrictMode, check https://react.dev/reference/react/StrictMode .
### New features
- Automatic CRUD backend generation