As I mentioned in https://github.com/farmOS/farmOS.js/issues/43#issuecomment-930338222, I've got a branch started for reporting errors from GitHub Action workflows, workflow-debugging. I had a bunch of tests failing last night for odd reasons, which I could debug via the GHA console b/c the test runner reported enough useful information. However I'm going to be working on a lot more AJAX soon, starting with #35 and #42. Errors there, especially if they are caused by a compatibility issue I didn't catch running the tests locally, will be especially hard to troubleshoot w/o some additional reporting, because the test runner only reports the HTTP status code, nothing else. So perhaps after I wrap up replacing the schema stubs (#26) I should make sure to add this reporting to all tests before I start that networking stuff.
As I mentioned in https://github.com/farmOS/farmOS.js/issues/43#issuecomment-930338222, I've got a branch started for reporting errors from GitHub Action workflows,
workflow-debugging. I had a bunch of tests failing last night for odd reasons, which I could debug via the GHA console b/c the test runner reported enough useful information. However I'm going to be working on a lot more AJAX soon, starting with #35 and #42. Errors there, especially if they are caused by a compatibility issue I didn't catch running the tests locally, will be especially hard to troubleshoot w/o some additional reporting, because the test runner only reports the HTTP status code, nothing else. So perhaps after I wrap up replacing the schema stubs (#26) I should make sure to add this reporting to all tests before I start that networking stuff.