Avoid writing implicit messages report #1140
Labels
Comments
badeball
added a commit
that referenced
this issue
Dec 17, 2023
This will become important in order to allow generating JSON / HTML reports *without* enabling messages. As explained in #1140 [1], we want to avoid touching the file system unless necessary. For pretty output, this is definitely not necessary. For JSON / HTML reports, this means a seemingly unrelated and implicit report appearing. [1] #1140
badeball
added a commit
that referenced
this issue
Dec 18, 2023
This will become important in order to allow generating JSON / HTML reports *without* enabling messages. As explained in #1140 [1], we want to avoid touching the file system unless necessary. For pretty output, this is definitely not necessary. For JSON / HTML reports, this means a seemingly unrelated and implicit report appearing. [1] #1140
badeball
added a commit
that referenced
this issue
Dec 19, 2023
This will become important in order to allow generating JSON / HTML reports *without* enabling messages. As explained in #1140 [1], we want to avoid touching the file system unless necessary. For pretty output, this is definitely not necessary. For JSON / HTML reports, this means a seemingly unrelated and implicit report appearing. [1] #1140
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The messages (ndjson) report is implicitly generated, as the json and html report are products of it (think a function - messages goes in - json and html comes out). With the introduction of a more stateful backend in v17.0.0 however, I think that the backend could contain this implicit state without touching the file system.
The text was updated successfully, but these errors were encountered: