Mathieu Decaffmeyer

The contributor created this PR while I was writing some major refactor when the library was in alpha. It was created in November 2020 so the code changed quite a...

Any plans on adding the extensions entry? It seems important to have error codes for the client to use: ```javascript switch (err.extensions.code) { case 'UNAUTHENTICATED': // ... ``` For now...

> Typically, if we need to change the strategy, I think it's okay to create a custom strategy, like you've done. But I understand the desire to use the default...

A function `cast_custom_types` won't be enough, that's why I suggested a behaviour to implement. And that's because the function `cast_all_fields/1` will include the custom type and try to cast it....

Thank you for the feedback. I think those with memory-limited system should update the IANA tzdata files manually. We could make it consume less memory, but would it then really...

@Brendan-csel I have added the following in the app (copy paste): ```jsx const App: VoidComponent = () => { function throwError(): string { throw new Error('A meaningful error message'); }...

I think in the last print screen, that first error log "A meaningful error message" is from the previous code without the error boundary. I think you might not have...

Here is the repo: https://github.com/mathieuprog/solid-router-error-boundary git clone [email protected]:mathieuprog/solid-router-error-boundary.git npm i npm run dev Console: > index.tsx:18 TypeError: Cannot read properties of undefined (reading 'length') at components.jsx:40:43 at dev.js:453:34 at untrack...

With Solid 1.6.9 (my error message is NOT lost): > index.tsx:15 Error: A meaningful error message at throwError (App.tsx:7:11) at get path [as path] (App.tsx:13:18) at Object.get [as path] (dev.js:1323:41)...

I switched to using `Show` to match on this condition. I tried to reproduce using the playground but can't, the real-world case also involves routing and other features - it...