Closed t1m0thyj closed 3 months ago
Attention: Patch coverage is 89.47368%
with 2 lines
in your changes are missing coverage. Please review.
Project coverage is 91.05%. Comparing base (
9e4a7e7
) to head (7b909b5
).
Files | Patch % | Lines |
---|---|---|
packages/zosfiles/src/methods/list/List.ts | 83.33% | 2 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
87.0% Coverage on New Code
0.0% Duplication on New Code
Release succeeded for the master
branch. :tada:
The following packages have been published:
@zowe/imperative@5.23.0
@zowe/cli-test-utils@7.24.0
@zowe/core-for-zowe-sdk@7.24.0
@zowe/zos-uss-for-zowe-sdk@7.24.0
@zowe/provisioning-for-zowe-sdk@7.24.0
@zowe/zos-console-for-zowe-sdk@7.24.0
@zowe/zos-files-for-zowe-sdk@7.24.0
@zowe/zos-logs-for-zowe-sdk@7.24.0
@zowe/zosmf-for-zowe-sdk@7.24.0
@zowe/zos-workflows-for-zowe-sdk@7.24.0
@zowe/zos-jobs-for-zowe-sdk@7.24.0
@zowe/zos-tso-for-zowe-sdk@7.24.0
@zowe/cli@7.24.0
Powered by Octorelease :rocket:
What It Does
Improves the way that invalid ds member names are handled. Before we tried to parse the invalid member names and replace control characters with �, which was prone to edge case problems. Now we stop parsing members after the first invalid member name is encountered, and add a fake member entry at the end that says "... N more members" for the ones we are unable to display.
How to Test
Run against our mainframe test system:
zowe files ls am {Timothy's PMF key}.COPYBOOK.UNTERSED
This data set contains thousands of members with special characters in the name 🙂Review Checklist
I certify that I have:
Additional Comments