Closed traeok closed 3 months ago
Attention: Patch coverage is 95.00000%
with 2 lines
in your changes are missing coverage. Please review.
Project coverage is 91.07%. Comparing base (
6778da5
) to head (5200c18
). Report is 1 commits behind head on master.
Files | Patch % | Lines |
---|---|---|
packages/imperative/src/config/src/ProfileInfo.ts | 95.00% | 2 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
My latest commit c488fab refactors the addProfileTypeToSchema
logic to add an optional parameter called updateProjectSchema
. We will not leverage this parameter when registering Zowe Explorer extenders - but, if extenders want to update a project-level schema, they can now do so by calling the API themselves. However, it will not be managed by a file such as extenders.json
until we add support for automatic updates of project-level schemas.
Should be ready for reviews now - I had to enhance one of the return checks to support updating the global schema while a project dir is open.
Issues
1 New issue
0 Accepted issues
Measures
0 Security Hotspots
89.3% 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.22.5
@zowe/cli-test-utils@7.23.6
@zowe/core-for-zowe-sdk@7.23.6
@zowe/zos-uss-for-zowe-sdk@7.23.6
@zowe/provisioning-for-zowe-sdk@7.23.6
@zowe/zos-console-for-zowe-sdk@7.23.6
@zowe/zos-files-for-zowe-sdk@7.23.6
@zowe/zos-logs-for-zowe-sdk@7.23.6
@zowe/zosmf-for-zowe-sdk@7.23.6
@zowe/zos-workflows-for-zowe-sdk@7.23.6
@zowe/zos-jobs-for-zowe-sdk@7.23.6
@zowe/zos-tso-for-zowe-sdk@7.23.6
@zowe/cli@7.23.6
Powered by Octorelease :rocket:
What It Does
Resolves #2086
How to Test
This one is a bit difficult to test on the CLI side because it relies on information from the source that initialized the ProfileInfo instance.
ProfileInfo
and callreadProfilesFromDisk
, specifying both a global dir and project dirProfileInfo.addProfileTypeToSchema
to add a new profile type to the global schemaYou can also test this through Zowe Explorer, but it requires a bit more setup:
npm run build && npm pack
in the imperative folderpackage.json
to resolve the local tarball containing the fixed Imperativeyarn fresh-clone && yarn && yarn build
zftp
profile type even though you have a workspace folder open (containing a proj. config)Review Checklist I certify that I have: