Hi, new to react so excuse my ignorance.
But why would you want to or need to save the api results in state for products?
Wouldn't it be better to just store them in a products list component or something similar? I'm not fully understanding why we would use redux for something like this.
@michael
-- because you want the product list to be a shared state.
For example, the product list is useful in a listing component - but it also might be useful in a checkout component that is validating that the product is still available.
Okay thanks. I'm just trying to understand what you guys take into consideration doing things this way.
I've never worked with any form of state management before trying out react. So the differences are confusing to me compared to my previous vanilla js frontends.
My article is more like an example how fetching data from an API works rather then a suggestion to do it like this in this exact case.
Deciding whether or not to put data in a store to share between components is totally up to your special usecase. Sometimes it makes sense, sometimes it doesn't.
For example, I work on a pretty big project right now and I decided to totally get rid of Redux. I only use the React Context API in the rare cases where I need to store data which is shared between components. For example in form handling.
Hi, new to react so excuse my ignorance.
But why would you want to or need to save the api results in state for products?
Wouldn't it be better to just store them in a products list component or something similar? I'm not fully understanding why we would use redux for something like this.
Thanks for the help in advance!!! :D
@michael -- because you want the product list to be a shared state.
For example, the product list is useful in a listing component - but it also might be useful in a checkout component that is validating that the product is still available.
Okay thanks. I'm just trying to understand what you guys take into consideration doing things this way.
I've never worked with any form of state management before trying out react. So the differences are confusing to me compared to my previous vanilla js frontends.
My article is more like an example how fetching data from an API works rather then a suggestion to do it like this in this exact case.
Deciding whether or not to put data in a store to share between components is totally up to your special usecase. Sometimes it makes sense, sometimes it doesn't.
For example, I work on a pretty big project right now and I decided to totally get rid of Redux. I only use the React Context API in the rare cases where I need to store data which is shared between components. For example in form handling.
I see! I'm always open to suggestions and best practices though and you seem to know you're stuff.
Just wanted to understand the thought process.
I'll look up this context api next. Thanks!