Closed noomorph closed 5 months ago
The idea is that we don't show the relevant file in the description (e.g. when hohoSetup.ts
, as a file inside setupFilesAfterEnv
fails while compiling):
The proposed solution is to parse stack traces (with a helper function or without), and use $.extractSourceCode(location[, includeComments])
to provide data for your custom markdown template.
The default logic "to show the entire test file contents" was removed because not everyone would be happy with it. It all depends on how you build your description template — if you use iframes or links, you won't be interested in this.
:tada: This issue has been resolved in version 2.0.0-beta.18 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Also, check what's the status of
setupFiles
... perhaps, we won't be able to track them properly in any case. 🤔That's where the environment-less mode of
jest-metadata
will shine.