remote functions: simplify status

[Rich-Harris]

simplifies get status and renames 'success' -> 'idle' since 'success' suggests finality (which might be okay for prerender but not for query or resources in general)

[changeset-bot]

⚠️ No Changeset found

Latest commit: c420084

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dummdidumm]

idle can also mean "didn't do anything yet", so it's not directly clear that something as available.

• Tanstack uses idle for its fetch status, but that doesn't mean data is loaded (https://tanstack.com/query/v4/docs/framework/react/guides/queries)
• Angular uses idle to mean "nothing happened yet" (https://angular.dev/guide/signals/resource#resource-status)

I like Angular's resolved for this more tbh.

[Rich-Harris]

'resolved' is the same as 'success' to me — it suggests a fait accompli. Hmm

[Rich-Harris]

'ready' maybe?

[jjones315]

settled is completely used when a Promise is no longer pending.

[Rich-Harris]

'settled' would be incorrect, because when used in a promise context it encompasses error states as well

[Beiri22]

available?

[Rich-Harris]

The maintainers discussed this offline earlier, and decided we're better off just removing status altogether in favour of independent loading and ready booleans. Between these and the error property you have all the information you need