Feat: Microcks-CLI v2 - IDE (Vs code) Integration and Local Dev Loop Enhancement
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- github-actions, go, vscode
- Domain
- ci-cd, cli, developer-experience, testing
Research direction
Start by reviewing the microcks-cli repository entry points for its current command-line, GitHub Actions, and test-result flows. The proposal describes three separate outcomes: a VS Code extension, a Testcontainers-powered local dry-run mode, and per-operation pass/fail annotations in GitHub Actions. Done means all three improvements are designed and implemented, but the issue does not identify files or tests to guide the work.
Written by the indexing model from the issue text.
Description
Reason/Context
- LFX Proposal
Description
The Microcks CLI (microcks-cli, written in Go) is a key part of Microcks' CI/CD story - it lets developers trigger contract tests and import artifacts from the command line and in GitHub Actions. This project goes into the developer experience layer. Today, developers must navigate to the Microcks web UI in a browser to see test results, check mock status, and diagnose import errors. There is no IDE integration, no offline validation mode, and no way to get mock results inline with the code being tested. This project builds three focused improvements that bring Microcks into the editor and the local dev loop: a VS Code extension, a local dry-run mode powered by Testcontainers, and an updated GitHub Actions output format that annotates PRs with per-operation pass/fail results.
Implementation ideas
No response
- Dominant language
- Go
- Stars
- 59
- Forks
- 74
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microcks/microcks-cli
-
Malformed local configuration is silently accepted and can be overwrittenPossibly taken @aniket866 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microcks/microcks-cli#615 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microcks/microcks-cli#610 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
microcks/microcks-cli#608 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microcks/microcks-cli#606 ·
Maintainers usually reply within 1 day
-
Windows test failures in MockFileSystem.Walk due to path separatorPossibly taken @dipak0000812 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microcks/microcks-cli#601 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microcks/microcks-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Waschndolos/open-clubmanager#185 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100