You are missing, idle or 'not-asked' state here.
Recently I got interested into Elm and what I really like about that community is that they promote data structure first approach for building apps.
For curious, have a look more in depth about ideas borrowed from Elm here lillo.dev/articles/slaying-a-ui-an...
I'm assuming the data fetch is made when you first enter the page, meaning that the 'idle' state will likely only show for one render - so is not worth handling.
Love the look of elm but never tried it!
Also, a common pattern that makes "idle" unnecessary on auto-loading states, is to start with the status as "loading" by default/definition.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You are missing, idle or 'not-asked' state here.
Recently I got interested into Elm and what I really like about that community is that they promote data structure first approach for building apps.
For curious, have a look more in depth about ideas borrowed from Elm here
lillo.dev/articles/slaying-a-ui-an...
I'm assuming the data fetch is made when you first enter the page, meaning that the 'idle' state will likely only show for one render - so is not worth handling.
Love the look of elm but never tried it!
Also, a common pattern that makes "idle" unnecessary on auto-loading states, is to start with the status as "loading" by default/definition.