Joseph Hale, MS SE

@github-actions [bot], this is still a valid, pending feature request.

@github-actions [bot], this is still a valid, pending feature request.

@github-actions [bot], this is still a valid, pending feature request.

> Does exporting from poetry and consuming in liccheck works for you out of the box? Yes. The following command sequence works great for me in all my Poetry projects....

This request seems even more valuable now that SPDX is the [de-facto standard](https://www.linuxfoundation.org/press/featured/spdx-becomes-internationally-recognized-standard-for-software-bill-of-materials) for licensing information.

Building off @rayniel95's [answer](https://github.com/jestjs/jest/issues/11698#issuecomment-1351991694)... Tests will [fail with a timeout](https://jestjs.io/docs/asynchronous#:~:text=if%20done()%20is%20never%20called%2C%20the%20test%20will%20fail%20(with%20timeout%20error)%2C%20which%20is%20what%20you%20want%20to%20happen.) if `done` is never called. ```typescript test('passing done fails after timeout if unused', (done) => { // This test will...

I just saw @atz3n's [workaround](https://github.com/jestjs/jest/issues/11698#issuecomment-1332760625) and decided to simplify it... ### Write a custom `fail` function ```typescript function fail(message: string = '') { expect(`[FAIL] ${message}`.trim()).toBeFalsy(); } ``` Full example ```typescript...

> There are already simple work-arounds like this in the thread above. There's also another way you've missed that it's inferior to the original `fail`: it simply doesn't work if...

After spending a few more hours on the problem this morning, I found a satisfactory solution using a [custom matcher](https://jestjs.io/docs/expect#expectextendmatchers) which builds off of the [`fail()` matcher from `jest-extended`](https://jest-extended.jestcommunity.dev/docs/matchers/fail). ###...

Our team had the same issue after we upgraded from Vue 2 to Vue 3. Since Vue 3 has [built-in support for fragments](https://v3-migration.vuejs.org/new/fragments.html#overview), we simply removed this package to fix...