Allow internal errors on BackendTask

[miniBill]

No description provided.

[netlify]

👷 Deploy request for elm-pages-todos pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	54b5fa4

[miniBill]

poke

[dillonkearns]

This looks really good! Is there any way we could add an automated test of some kind to the CI? Could be something like just running an elm-pages script in CI and checking the output.

[miniBill]

I've pushed a piece of test.sh that runs a script that will generate an internal error, but I'm not sure how to check the output from there

[dillonkearns]

The two options that come to mind are:

1. Write a JS test (there are some examples in https://github.com/dillonkearns/elm-pages/blob/master/generator/test/route-sorting.test.js#L1-L2). They could use NodeJS to run the script and capture output and use the vitest test helpers to assert on the output. Could even use https://vitest.dev/api/expect.html#tomatchsnapshot.
2. Use an elm-pages script as a test harness to execute the test script and check its output. Not sure if this is too self-referential or not, though, but seems like it could possibly work out decently.

[miniBill]

Ok, implemented a line in test.sh that checks for the internal error. Pre-patch that code would just explode