Closed traeok closed 1 month ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 92.68%. Comparing base (
6370958
) to head (19b920f
).:exclamation: Current head 19b920f differs from pull request most recent head 4c0b248
Please upload reports for the commit 4c0b248 to get more accurate results.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Sorry to anyone that was trying to test on macOS - I needed to make some changes to fix extracting portable VS Code versions. I've ran some manual tests with the latest changes and all seems to be working as intended now 😅
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
No data about Duplication
Hey @traeok I don't see any instructions in the description on how to package and install the new package. I ran build and package as usual but don't see anything new included after the command. It may be good to add these steps to our dev/top-level README for contributors to also know how to use it.
Sorry about that @JillieBeanSim, I added a section in the zedc
readme but forgot to add the steps in the PR description. I've updated the PR with steps on how to install 👍
Proposed changes
This branch proposes the introduction of a lightweight development CLI made in Rust, providing the following commands as helper utilities:
setup
node_modules
pm
test
- test a local VSIX or an artifact from GitHub using a Git refZOWE_CLI_HOME
set to the sandboxed directory (so it doesn't affect your global configuration)Developers can leverage this utility while developing a Zowe Explorer bug fix/feature, or for testing other contributions without modifying their original environment. It's entirely optional and does not interfere with normal behavior of the repo, so developers can choose to adopt it if they find it useful.
Other ideas that I had in mind for the future of this tool:
secrets
commandtest
command--integration/-i
for running integration tests using WebDriverIOwdio.conf.ts
, the CLI could handle the change for you and then restore it after the tests are completeInstallation steps
cmake, gcc
, Git Bash and Rustcd
into thezedc
folder in the root of the repo and run the commandcargo build --release
.zedc
tool that can be added to your PATH environment variable.zedc
command. A help message should appear with the available commands.Release Notes
Milestone:
Changelog:
Types of changes
What types of changes does your code introduce to Zowe Explorer? Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This checklist will be used as reference for both the contributor and the revieweryarn workspace vscode-extension-for-zowe vscode:prepublish
has been executed