A Practical Guide to JavaScript Proxy Objects 

Tom you always have great content. Came across JS Proxy today and needed to understand it. Checked a few videos but this was the best. Tom always saves the day!

This guy is a legend

naming the proxy getCharacter is kinda rough, it really undermines the understanding. Calling it "characterProxy" would make vastly more sense, esp. as you expand the functionality of the proxy. Secondly, it may be a matter of form, but I would always use target instead of the original object when using the proxy. I think proxies are recursive, so you can proxy a proxy etc... one of your implementations refered to the original object directly, bypassing future flexibility. all-in-all a decent run through, with just those minor nit picks.

Nice!

Good video, nice to here an Australian voice instead of always American voices

13:17 don't need the Boolean just to wrap it in ( )

Thank u for this guide, tho i have a question. Why write 'complicated' proxy obj instead of a function which will check if an item with ID passed to our fetch function already exists in our cache? and just return if it does?

This is a good explanation thanks for that, but why would be one using this approach of getter and setter isn't this approach more relevant towards object oriented whereas JS is functional ?

How you set the value , if handler dosent have the set mothod... ??? 😵‍💫

This is actually bad Don't recommend watching it, you'll ruin your understanding of the purpose of proxies Great channel overall, but this video is bad I'm sorry

All you need to get the `in` operator working is the grouping operator. if( !(1 in getCharacter)) { } It is not the case that:- if( !1 in getCharacter) - is falsey all the time. `!1` is converted ToBoolean to false. Thus, the expression is literally evaluated as:- if(false in getCharacter) - and, given that id's are numeric here, `false in getCharacter` will literally be false all the time.