microsoft / component-detection

Scans your project to determine what components you use
MIT License
396 stars 81 forks source link

Go With Replace Detector no File Parsing #1181

Closed amitla1 closed 1 week ago

amitla1 commented 2 weeks ago

Remove the file parsing for the replace section of the file The current go detector and the new go detector that has the replace module sometimes detect a different number of components and they should be the same number. The file parsing logic that was changed in the new go detector couldve impacted this therefore reverting that change and just implementing replace logic for CLI and not parsing a file

codecov[bot] commented 2 weeks ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.2%. Comparing base (dafe527) to head (4d84159).

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #1181 +/- ## ======================================= - Coverage 76.3% 76.2% -0.1% ======================================= Files 257 257 Lines 11495 11440 -55 Branches 1156 1147 -9 ======================================= - Hits 8772 8723 -49 Misses 2384 2384 + Partials 339 333 -6 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

github-actions[bot] commented 1 week ago

👋 Hi! It looks like you modified some files in the Detectors folder. You may need to bump the detector versions if any of the following scenarios apply:

If none of the above scenarios apply, feel free to ignore this comment 🙂