I believe there are a few things that I would have done differently and I am sure that implementing them could win you bonus points: 1. One of the wrapping elements can be replaced with a element and then the handleLogin can be passed to the onSubmit prop of the form. The then becomes a type="submit" button and doesn't need the onClick prop. 2. Probably it makes sense to clear the error if the user starts to change one of the fields again. 3. Also, I would use a nulll value when there is no error - it makes more sense for it to be null as this means that there is no error. An empty string for an error might indicate an error that doesn't have a description or some kind of an unknown error. I know that probably won't happen in real life, but it's a good practice to differentiate between null and an empty string. 4. setLoading(false) can go at the bottom, after the try/catch, instead of repeating it in both the try, and the catch. There's no need to place it inside. Alternatively, it can go in the finally clause of the try/catch block. 5. I personally take naming very seriously. disableButton sounds more like a name for a function that when called would disable the button. Probably would be better to call it isButtonDisabled.

This is so helpful!! I’m busy completing an advanced React course and this is such a great way to measure where I’m currently at! Please don’t stop making these vids, it has so much value!

Thank you Peter. I tried solving the challenge before you did it and was able to solve it in 16min 30s. I had a bunch of hiccups which slowed me down but I'm glad I was able to solve it.

After doing a few take-homes and live interviews lately; I've thought that it would make a cool youtube series/channel to collect them from devs doing interviews. Maybe with two formats. One video where it's new to the dev and then a second video with a "designed" solution. Cool to see a little peek of your freelancing progress too! 👍🏼👍🏼

really good content Peter..it is helping me a lot to learn front end technology because you deal with concepts and understanding more than routine tutorial walkthrough

Well done Man can you upload more React Interview Questions like that but more harder?

Thank you! This is exactly the type of react content I’ve been looking for. Appreciate it

Instead of adding setLoading false in two places in both the try and the catch, you could've added a finally block and added it to that.

thank you! this is super helpful :) especially the trick with 'disabledButton' variable, I've been using conditional rendering based on 'loading' value, but that's a lot more neat, thanks again!

great video!

great, I've go over the 15min but I got it. If you have more like this, it will be so helpful! thank u very much for sharing

I've been looking for a video like this, thanks

Awesome exercise Peter, thanks a lot!

great content, more interview live challenges like this are really helpful👍

Keep them coming Peter!

Thank you ... please make more videos on real react coding challenges

Good one! Thank you for the content.

great video man thank you. all well and good!

Thank you. Your content is amazing! 🤗

So good! Thank you@

Hey Peter, Thanks a lot for making this video. I would request you to please release more such type of live coding vide. It is very useful. Once again Thank you so much.

good to see these videos

this was a quite chill and easy challenge, managed it in roughly 8 mins (including fixing the dependency tree which was outdated for today's standard due to node major version change) for those wondering, just input these commands on first install if you're running node v17+: >npm i >npm audit fix --force >npm update then just do the normal npm start and it should run fine. cool stuff that i find better than what was shown on vid: i did the button disabled by: which is way quicker than declaring a whole ass const. and the div was only shown by doing this: {error !== '' ? {error} : null} which is the most appropriate way of doing what was asked.

Thanks a lot. Dope, spot on, practical.

Hey! Thank you for uploading this, very useful :) Could you please tell me where to find such challenges?

absolutely fantastice content. please make more

Hi, thanks for the video. I saw that you have 4 declaration of useState(). Would it be recommended that I use useReducer() for this problem instead?

I really like this exercise.

That was great!!

useState seems unnecessary for the email and password? why can't you just access the email and password inputs from the html element on button click?

This is fairly simple and I can probably do it in that amount of time, but I'm sure to fail if you give me time limit and have someone watch me code. 😢

Awesome stuff! The zooming is completely unnecessary and super dizzling hahaha but cool stuff absolutely, thanks! And by the way, what software do you use to do that? Can it write on screen while you are recording?

this is amazing

SetError("error, something went wrong") could be a quick interview fix I guess... Awesome video mate , thanks

Great video ❤️

interview for entry or junior right

Amazing

great!! thanks!

Want more of this type of video

Great, Thank you

How is the disableButton variable constantly being updated on input change?

Is this junior dev interview?

Thankfully this is just a question. For me i won't recommend it on production. Since if i'm correct you are re-running the state every time. Also technically you can set the initial state of error to null or something.

Hooks are still cool? Or something changed?

how do you start the project on the browser?

what is a COOING challenge?

Impressive.

Why am I the only one who loves Blazor?! It's React but statically typed in so no more imports, boiler-plate, intellisense is kosher, etc.. I feel so alone :(

Just a little suggestion.. Maybe do a little less zooming in and out of the screen, it can get somewhat frustrating especially on higher playback speeds.

Just do final{setLoading(false)}

grreat

You have used disabled attribute and setting it using variable...cant we use something like events.target.disabled = true?...what is the difference in these 2 approaches

useState causes re-renders on every keystroke for email and password. Wouldn't useRef be better in this example over useState? Also, if keeping handleLogin inside component like that, I would place it inside a useCallback since you're re-rendering and redefining the function on every keystroke.

these are all things you learn day one

Well, this takes like 20 minutes from me...

i don't know what position you have actually interviewed for, to get this kind of problem set, but from my experience, real life interviews are nothing like this. This is basic beginner stuff, that a technically versed guy, that played with React for a weekend would nail. Once again, not trying to be negative, just sharing my personal experience, both as interviewee and interviewer.

I like your solution but it is very verbose. You took way longer to solve it, not only because you're obviously explaining what you're doing (which is expected in an interview), but because you're defining a lot of useStates. I merged them all down into three single useStates and was able to do it extremely fast: const [{ email, password }, setInput] = useState({ email: '', password: '' }); const [loading, setLoading] = useState(false); const [{ hasError, errorMessage }, setError] = useState({ hasError: false, errorMessage: '' }); Then I handle the error like this instead: function handleLogin() { setLoading(true); login({ email, password }) .then(() => { alert('Successfully logged in'); setLoading(false); }) .catch((e) => { setError({ hasError: true, errorMessage: e.message }); setLoading(false); }); } So notice how everything is just bundled up together so I can use them as I please. Now I despise JavaScript so I would've preferred for it to be in TypeScript haha.

Why inputs attributes are inside parenthesis {} and double quotes "". SHouldn't they be inside double quotes only ""?

Great man! Just a tip, I think you could use finally clause on try catch to setLoading() in it. So, it will be called every time independent of the result

Great, thank you