resource.error works unexpectedly
Consider this sample: https://playground.solidjs.com/anonymous/095fcbf7-6807-4c6b-ac41-223a5f2fde21
Per docs:
data.error: if the request has errored out. createResource: provides an Error object for data.error. It will show even if the fetcher throws something else. If the fetcher throws a string, data.error.message will contain that string.
I would expect the div with the error string be rendered to the dom but its not the caseSolid Playground
Quickly discover what the solid compiler will generate from your JSX template
7 Replies
the catch the error you might want to look into https://docs.solidjs.com/concepts/control-flow/error-boundary
Error boundary - SolidDocs
Documentation for SolidJS, the signals-powered UI framework
and inside it call the resource
{test()}whats the point of the .error field if im supposed to use the ErrorBoundary
In my use case I would rather avoid using the error boundary because my layout looks something like this:
I want those two divs to be always rendered. If I were to wrap that component in an error boundary it would replace it alltogether
I will first start with the proper usage
at least for having better understanding
there are 2 issues with your original code
if you want to just show the error in the templte
first your create resource needs to be an async function
second to avoid accessing the error before it is ready, you need optional chaining at least
{test.error?.message}Oh! That does it, thank you! :)
but you might have issues with {test()}
to use it when it throws you will need to wrap it in try catch sort of logic
Yeah, its not exactly how I use it like in the example, wanted just to show my point, the only issue I had was why was there nothing in the .error. I handle {test()} manually