microsoft / microsoft/component-detection
Non-existent filepaths reported in manifest.json
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
We are seeing an issue where CD is reporting components under a file path that _does not exist on disk_.
This specific case is with csprojs, though we have seen the same thing with NPM package.jsons.
The correct location of the csproj is `repos\repoName\design\redacted\redacted\redacted.csproj`, but CD is reporting the file path as `repos\repoName\design\redacted\redacted.csproj`.
This is from running CD 5.1.8 locally on a Windows machine with the following arguments: `scan --SourceDirectory="path\to\repoName" --ManifestFile "path\to\output\manifest.json" --Output="path\to\output" --Timeout=60`.
Contributor 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.
Research direction
Reproduce the report with the supplied CD 5.1.8 scan command on Windows, using a repository containing nested .csproj and package.json files. Start by tracing how the scan builds manifest.json paths from the source directory. Done means reported component paths match the files' actual locations on disk for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100