Issue To Be Solved
GitHub Actions should add a custom linter to check map ranges.
Suggested Solution
Great suggestion by @turbolent
In Cadence we're using a custom linter to reject such cases (https://github.com/onflow/cadence/tree/master/tools/maprange), we might want to also use it in the atree repo?
Given that GitHub workflows can consume a lot of time, one approach is to download precompiled binaries of the custom linter(s) from Cadence repo (same way golangci-lint binaries can be downloaded from their repo).
E.g. https://github.com/golangci/golangci-lint/releases/tag/v1.53.3
Issue To Be Solved
GitHub Actions should add a custom linter to check map ranges.
Suggested Solution
Great suggestion by @turbolent
Given that GitHub workflows can consume a lot of time, one approach is to download precompiled binaries of the custom linter(s) from Cadence repo (same way golangci-lint binaries can be downloaded from their repo).
E.g. https://github.com/golangci/golangci-lint/releases/tag/v1.53.3