react-notifications | Notification component for ReactJS | Notification library

Figured it out! I wrongly assumed that the verificationId passed back from verifyPhoneNumber() was the raw code and I didn't want to save that in a local state on client side as I saw that as a security vulnerability. Fortunately the verificationId is not the raw code to be entered, but rather a JWT or something that is abstracted, so I just saved that value in the React state which was then referenced by a separate function getAttemptedCode(values) which is called only after the user clicks submit on the attempted code.

If anyone find this method I found to be a security vulnerability let me know please!

This is the expected behavior due to React's reconciliation algorithm. While you think of it as removing one input and adding another one, what React sees is that there's still an input field, just with changed id and placeholder attributes. It doesn't unmount the element and mount a new one - it's just a change in props. This is reflected in the DOM - React keeps the same input element and only changes its attribute values.

To avoid this, you can give them different keys.

i added two folders that was missing 'transversal-administration', 'transversal-translation' in the past i have just only: ['app']. the loader in the past load just the app folder

Input in react-validation lies under build folder. But from the error it seems that you didn't imported Input properly: SyntaxError: E:\Projects\personal\rental-application\node_modules\react-validation\src\components\input\index.js: Support for the experimental syntax 'jsx' isn't currently enabled (6:3):

Can you please check your import statement? It should be something like this:

You need to create dedicated component for

All you need to do is create the file and create a function in that file. This question has an answer that explains it

How to create helper file full of functions in react native?

you need to create the file validation.js

then

The most current version of react contexts isn't available until version 16.3 while you are using version 15 (on the frontend). You should update to version 16.3/greater or use the legacy version documentation if you cannot update. https://reactjs.org/docs/legacy-context.html

OK, I figured out the issue. I thought the error was telling me that path was undefined. When it fact it was saying the variables passed into path.join() were undefined. And that was because I forgot to add in my .env file to the root so it could grab those variables. Whoops!

You can not use a Hook inside a react Class.

Hooks are functions that let you “hook into” React state and lifecycle features from function components. Hooks don’t work inside classes — they let you use React without classes. (We don’t recommend rewriting your existing components overnight but you can start using Hooks in the new ones if you’d like.)

• https://reactjs.org/docs/hooks-overview.html#:~:text=Hooks%20are%20functions%20that%20let,if%20you'd%20like.)