For some reason I do not get an error in the console with the link to the Firebase console. I tried to create the index manually, but that doesn't seem to work.
Hey Nick, How would we prevent fetching the same product after it already appeared on the screen to prevent excessive reads from Firestore? Some context if you use print statements that are fetched it shows each time a new filter appears. If I don't hear from you here I'll hit up discord
It depends on your implementation. You could have a local check “if product is loaded don’t fetch”. Or cache the query locally and check the cache. I’m not sure if that helps… This is definitely an area that I wouldn’t be hyper concerned about prematurely optimizing.
@@SwiftfulThinking yeah was thinking that as well about prematurely optimizing… I’m reading too many horror stories about firebase charging users an extreme amount of money because of excessive of reads etc … lol … thanks for the advice
About 17 minutes in String is added to the CodingKeys enum. This is not necessary. Once the CodingKeys enum is exposed in our code we have access to .stringValue. So in our code we can write Product.CodingKeys.title.stringValue. I discovered this while working from the video. Thanks
Learning so much in this Firebase series, going to be implementing Firebase/Firestore in my own personal app!
AWESOME video but agh 11:24 I needed to populate and grab all the categories without declaring each in an enum!
Not going to lie your videos are really informative and clear ....Firebase should sponsor your videos lol...Peter Friese hope you're watching
Nick's videos teach better than Firebase Tutorials. Then don't even explain this deeply. They do it like a robot. lol
For some reason I do not get an error in the console with the link to the Firebase console. I tried to create the index manually, but that doesn't seem to work.
I had the same problem
Please make a video on updating a document using the auto generated Id from Firestone. 😅
Hey Nick, How would we prevent fetching the same product after it already appeared on the screen to prevent excessive reads from Firestore? Some context if you use print statements that are fetched it shows each time a new filter appears. If I don't hear from you here I'll hit up discord
It depends on your implementation. You could have a local check “if product is loaded don’t fetch”. Or cache the query locally and check the cache.
I’m not sure if that helps… This is definitely an area that I wouldn’t be hyper concerned about prematurely optimizing.
@@SwiftfulThinking yeah was thinking that as well about prematurely optimizing… I’m reading too many horror stories about firebase charging users an extreme amount of money because of excessive of reads etc … lol … thanks for the advice
i think this is very fast method to use the DB, but the DB cost is will not too much ?
I sense you will make a video that involves "Stripe" in the future.
Great video as always!
Can you teach how could I apply nested filters? Like filter by smartphone and price range between 500 ~ 700 at same time for example
.whereField has an isLessThan and isGreaterThan you can put both for your 500 to 700
Thank you sooo much, mr. nick. 🙏
Nice video great effort 🎉
Awesome, thank you so much!
brother go to bed!
About 17 minutes in String is added to the CodingKeys enum. This is not necessary. Once the CodingKeys enum is exposed in our code we have access to .stringValue. So in our code we can write Product.CodingKeys.title.stringValue. I discovered this while working from the video. Thanks
Learning so much in this Firebase series, going to be implementing Firebase/Firestore in my own personal app!