karuppiah7890 / karuppiah7890/tce-e2e-test
Linters
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We need linters to check some basic stuff. To start off, we can use `golangci-lint`. We might have to use some custom built linters too, or other third party linters to get some of the below features
- We should almost always use our `log` package and not the standard library `log` package
- We should never use "/" as file path separator in our code and instead use `filepath.Join()` always from the `filepath` standard library
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the repository's Go code and deciding how golangci-lint should be configured. Check how the custom rules would identify use of the standard-library log package and slash path separators instead of filepath.Join(). Done means the requested lint checks run consistently and flag the stated patterns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100