getappmap / getappmap/appmap-js
Installer: User is instructed to manually validate AppMap configuration when the verification step fails
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Give users an option to manually validate the AppMap configuration when the installer cannot complete this step instead of ending with an error.
Example: when Maven command not available in the installer's environment, it cannot be used to validate that the AppMap configuration is OK - users will have to complete that steps in IntelliJ.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No file or test is named. Start by locating the installer’s AppMap configuration verification flow and the branch used when Maven is unavailable; then determine how IntelliJ-based manual validation is communicated. Done means the installer offers that fallback instead of ending with an error, and the behavior is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100