Maybe that wording is a little strong, but I don’t think it’s wrong. I know TanStack Query best, so I’ll talk about that. TanStack Query doesn’t really have an opinion on ADTs. It’s very React-ish: if your data is loading, show a loading spinner. If your data is defined, show the data. Otherwise, show an error. This is weak modeling. It’s really shaped more like this (pseudocode): type RemoteData = Idle | Loading | Success Data | Failure Error You don’t have “data or undefined.” You have a remote data type that you need to unwrap. This is a powerful shift in perspective. You can map over this remote data ADT. You can pattern match and handle every variant. You can combine remote data values. This results in real clarity and ergonomics gains in a React codebase. At August Health, we built a whole QueryResult ADT around TanStack Query to get those benefits. It’s around 1700 lines of code, with tests. Conversely, Effect Atom gives you this for free because effectful Atoms give you a Result type: github.com/tim-smart/effect-… This is just one example, but I’m sure there are others. There’s an inescapable seam between TanStack and Effect, and that seam always ends up being yours to create and maintain.

i would say it's a skill issue by RemoteData, can return a memoized one. I think learning a few "representations" in melange can be a pain but it's similar to writing bindings... if we would own the lower layers (react.js in this case) we won't have this issue at all

Flicker-free loading of remote data in your @safe_stack apps? The RemoteData type gets the job done! In this blog post, we discuss the SAFE.Server package, including some recent improvements. #dotnet #webdev #fsharp @fsharponline buff.ly/4h5onbf

Using derived data? or Signals? Want to make a conditional request or effect? You can achieve this by *deriving harder* For example, if you know of a situation that would cause "RemoteData" to error, don't access it.

Our revolutionary system, called 'Amrit,' is an IoT-based water monitoring solution with an embedded sensor designed to precisely monitor water quality and quantity. #SmartWaterManagement #WaterInnovation #watertechnology #watermonitoring #Waterqualitymeasurement #remotedata

And it's probably better written in an ad hoc way. For instance RemoteData is a great idea, but not a good package, because you need more/less data/states than it provides, yet it's much harder to edit than a local custom type.

I am not aware of any in a form of package, although we are having something like that in our codebase. Well more or less it is a RemoteData without the NotAsked variant, but it has the same shape :D

Oh, I have no idea, nor do I care about runtime. I just want to TypeScript to let me know if I did it right or not at compile time. I'm curious why you're asking? Here's what I got from TypeScript playground... This code: type WaitingOnUser = { type: 'waitingOnUser' } type Loading = { type: 'loading' } type Failed = { type: 'failed', error: string } type Success = { type: 'success', data: Array<string> } type RemoteData = WaitingOnUser | Loading | Failed | Success const succeeded:Success = { type: 'success', data: ['uno', 'dos']} console.log(succeeded) const didSucceed = (remoteData:RemoteData):boolean => { switch(remoteData.type) { case 'waitingOnUser': return false case 'loading': return false case 'failed': return false case 'success': return true } } console.log(didSucceed(succeeded)) Compiles to: "use strict"; const succeeded = { type: 'success', data: ['uno', 'dos'] }; console.log(succeeded); const didSucceed = (remoteData) => {     switch (remoteData.type) {         case 'waitingOnUser':             return false;         case 'loading':             return false;         case 'failed':             return false;         case 'success':             return true;     } }; console.log(didSucceed(succeeded));

Tune in during GCC 2023 tomorrow to hear about the latest work to enhance remote data access in @GalaxyAustralia from the team at @MelBioInf and BioCommons #UseGalaxy2023 #remotedata ⌚11.20 am AEST 🗓️ Wed, July 12

I have solved this use case a while ago with the RemoteData data structure. It'll work with signals out of the box. Perhaps a couple directives could be created to simplify interacting with the RemoteData object wrapped in a signal: github.com/DmitryEfimenko/ng…

I've decided that every time I make a demo on limber.glimdown.com, I'm going to add it to the tutorial Today: RemoteData - fetching: tutorial.glimdown.com/11-req… - a less-visually stimulating / overwhelming loading pattern: tutorial.glimdown.com/12-loa… #EmberJS #JavaScript #Tutorial

Are you a #dataanalyst with a passion for uncovering insights and driving business growth? We have several remote positions available for data analysts with experience in SQL, Python, and R. 📊👩‍💻💻 #DataAnalysisJobs #RemoteData

Sum types make this so much easier to handle (including data and error content): type RemoteData e a = NotAsked | Loading | Failure e | Success a

Docs for RemoteData here: ember-resources.pages.dev/fu…

Avoiding boolean flags and impossible states when using declarative data fetching with React and #Typescript #frontend #webdev #dormosheio #reactjs #reactquery #remotedata #javascript #frontenddev dormoshe.io/trending-news/-a…

At work we use of RemoteData data structure. I had written an article about it. I wish this pattern was more widely adopted, but my reach to the community is not wide enough. Perhaps you'll find this useful for the community. Sorry for the shameless plug medium.com/angular-in-depth/…

Made a demo of using the `RemoteData` resource in #EmberJS' strict-mode <template>s. #JavaScript #REPL Live / interactive demo/REPL here: Person ID