mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-10-05 14:46:55 +01:00
Preserve literal strings in composed report acceptance
This commit is contained in:
parent
aecd081778
commit
5d1399f9fb
4 changed files with 73 additions and 10 deletions
|
|
@ -154,7 +154,8 @@ not a deployable or compiled application.
|
|||
## Before opening a PR
|
||||
|
||||
From your BCQuality checkout, use the existing validators. The Python
|
||||
validator needs Python and PyYAML; the fixture harness needs PowerShell 7.
|
||||
validator needs Python and PyYAML; the fixture harness needs PowerShell 7.5 or later
|
||||
so findings-report parsing preserves timestamp-shaped JSON strings verbatim.
|
||||
If PyYAML is not installed in your development environment, install it with
|
||||
`python -m pip install pyyaml`.
|
||||
|
||||
|
|
|
|||
|
|
@ -78,6 +78,9 @@ its own task-level applicability and reports `not-applicable` or
|
|||
|
||||
## Composition acceptance
|
||||
|
||||
The findings-report validator requires PowerShell 7.5 or later to preserve
|
||||
literal JSON strings with `ConvertFrom-Json -DateKind String`.
|
||||
|
||||
A report can be internally consistent while omitting a selected review. Bind
|
||||
the final acceptance gate to the host's selection, not just the returned
|
||||
reports. The private JSON input to `-ExpectedCompositionPath` follows the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue