Bug: state.matches is not a function if the state status is "error"

[alita-moore]

XState version

XState version 5

Description

currently, if I do the following

useSelector(state => state.matches("Saving"))

and the machine currently has an "error" status matches is not defined on state.

This buries the lead, the problem is something in my machine but then I'm getting a type error because react can't call this function.

Expected result

matches remains defined

Actual result

matches is not defined

Reproduction

https://stackblitz.com/edit/react-ts-playground-6bydbzce?file=index.tsx

Additional context

No response

[davidkpiano]

state.matches(…) is really meant for state machine snapshots, not promise or other snapshots where .value is not defined. Are you seeing this in snapshots from state machine actors too?

In general, you can always compare against state.value directly (i.e. state.value === 'saving' or use matchesState('saving', state.value).

[alita-moore]

seems I wasn't precise, the error is when something goes wrong in the "input" of the context that causes the regular actor to enter an error state: https://stackblitz.com/edit/react-ts-playground-vfk6bmzo?file=index.tsx