Please provide best practices for fixes configuration in Golang, considering version existence and monorepo architecture.

[flc1125]

I hope to achieve the following effect with a single configuration. I have repeatedly tested many different configurations, but I have been unable to achieve the desired result.

github.com/go-fries/fries/{package}/v3::cache/ -> {package}/

Currently, I am using a rather cumbersome method, which involves generating through scripts and listing all the packages one by one. Please see my configuration: https://github.com/go-fries/fries/blob/6c8a0a1fe759090809bca66348450c0a6aee6ca2/codecov.yml#L22-L88

However, I don't think it is very good. Whenever I add a new package or adjust the directory structure, it needs to be changed accordingly.

Therefore, I would like to ask whether there is a better way to achieve my desired outcome.

Thanks.

[VinGarcia]

Hey @flc1125, I use codecov for my open-source projects. In particular one of them has several submodules and it works fine just by using the default configs. I only use the codecov.yml to ignore a few internal directories:

https://github.com/VinGarcia/ksql/blob/master/codecov.yml

The trick is that codecov will automatically look for files called coverage.txt, so in this script I just force all the tests to run and produce separate:

https://github.com/VinGarcia/ksql/blob/master/scripts/run-all-tests.sh

You will probably only need the -coverprofile= arg in your case, in mine everything is about the core module, so I have configure the coverage output in a different way.

Finally on the CI I just run the script then the codecov upload script or action:

https://github.com/VinGarcia/ksql/blob/master/.github/workflows/ci.yml#L30

[flc1125]

@VinGarcia Thank you for your answer. As you mentioned, we only need to generate coverage.txt, and it will automatically find and report.
But my situation is a bit different. Most Go components are similar to version v1, meaning the go mod path and the directory path are basically aligned.

In my case, each go mod version is {package}/v3, but the actual relative directory doesn't include v3. Similar to the issue I mentioned: github.com/go-fries/fries/{package}/v3::cache/ -> {package}/. It fails to locate the corresponding test files in the mapped directory, causing incorrect coverage results.

If I were to express the effect I want using regular expressions, it would be very similar to this situation:

^github\.com\/go-fries\/fries\/([^(?:v3)]+)\/v3::$1

see: https://regex101.com/r/wOllBa/3