getappmap / getappmap/appmap-js
exclude pattern can be used to filter out AppMaps from in the archive
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Note Not ready for implementation. Deleting the AppMaps before running the archive action may be a suitable workaround.
The build may sometimes produce AppMaps that the user doesn't want to archive or analyze.
Add a CLI option appmap archive --exclude which may be repeated. Each option value is a directory name or file name to exclude from the archive.
Checklist:
- Define the CLI option.
- When building the archive, ignore directories and files that match the option.
- Implement a test(s) as appropriate.
- Publish a pre-release build of this command so that the
archive-actionCompanion PR can be tested with it.
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
Start at the appmap archive CLI entry point and trace how files and directories are selected for the archive. Define the repeatable --exclude option, verify matching files and directories are omitted with tests, and publish a pre-release build for the linked archive-action Companion PR to test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100