I'm Drew Town a web developer and systems engineer in Colorado. Always learning, traveling and exploring. Sharing updates, trials and tribulations in tech and life.
Just curious why you decided to create promistate? There are a few other I have seen that do similar things (such as vue-promised) and I was curious as to what you would consider the main differences to be?
Error boundary is a really good tip and one that I personally way under-utilize. I'm definitely going to try and incorporate that into my projets more.
It's a more low level approach that allows devs to implement their own version of vue-promised (if they want to), also works nicely with things like form submits where you need similar properties.
Just curious why you decided to create promistate? There are a few other I have seen that do similar things (such as vue-promised) and I was curious as to what you would consider the main differences to be?
Error boundary is a really good tip and one that I personally way under-utilize. I'm definitely going to try and incorporate that into my projets more.
It's a more low level approach that allows devs to implement their own version of vue-promised (if they want to), also works nicely with things like form submits where you need similar properties.
Also, it seems like promisestate is framework agnostic and front-end/back-end agnostic, right? So you can re-use it where-ever you want.
Yup, that's true as well!