@DFanso Hi, I have a question about this bug. I implemented a rate limiter — should I write a unit test for it? If yes, based on the project structure, can I create a test file named createMsg_test.go under the cmd/cli folder?

I made it in my side and it shows me like this:

yang@Mac commit-msg % go test -v ./cmd/cli
=== RUN   TestGenerateMessageRateLimiter
    createMsg_test.go:43: Successful calls: 10 out of 10
--- PASS: TestGenerateMessageRateLimiter (1.00s)
PASS
ok      github.com/dfanso/commit-msg/cmd/cli    1.246s
yang@Mac commit-msg % 
yang@Mac commit-msg % 
yang@Mac commit-msg % go test -v ./cmd/cli
=== RUN   TestGenerateMessageRateLimiter
    createMsg_test.go:43: Successful calls: 100 out of 100
--- PASS: TestGenerateMessageRateLimiter (19.00s)
PASS
ok      github.com/dfanso/commit-msg/cmd/cli    19.248s
yang@Mac commit-msg %

The structure will be like:

## Structure

commit-msg/
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── assets/
│   ├── commit-msg-preview.gif
│   └── image.png
├── cmd/
│   ├── cli/
│   │   ├── createMsg.go
│   │   ├── createMsg_test.go    # New unit test file for rate limit
│   │   ├── llmSetup.go
│   │   ├── root.go
│   │   └── store/
│   │       └── store.go
│   └── commit-msg/
│       └── main.go
├── commit
├── go.mod
├── go.sum
├── internal/

If you think the structure is okay to you, I will make a pull request for you to make code review.
Or if any other I should provide and/or improve, please let me know, thank you.

[BUG] Potential Race Condition in Concurrent API Calls #85

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions