Skip to content

Commit f0310dc

Browse files
authored
Fix typos and lint errors to pass golangci-lint (#902)
* recieves -> receives * Allow unused variables for a proposal doc
1 parent 109c324 commit f0310dc

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

docs/proposals/0845-scheduler-architecture-proposal/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ Picker selects the endpoint(s) from the provided list of scored endpoints. Picke
6868

6969

7070
### PostSchedule
71-
PostSchedule recieves the output of the result(s) of the scheduling cycle(s) and makes sense of the data to be consumed by the calling system.
71+
PostSchedule receives the output of the result(s) of the scheduling cycle(s) and makes sense of the data to be consumed by the calling system.
7272

7373
### PostResponse
7474
PostResponse is a special case extension that can optionally be implemented by a plugin that needs to augment its state based on response or request data. This should only be implemented for plugins that need to update state outside of the scheduling cycle. PostResponse is ran at the time of processing a response.

docs/proposals/0845-scheduler-architecture-proposal/interfaces/interface.go

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,11 +36,11 @@ type Endpoint struct {
3636

3737
type EndpointState struct {
3838
// storage is per Scheduling Cycle, and so has no thread-safe concerns.
39-
storage map[string]any
39+
storage map[string]any //nolint:unused
4040
}
4141

4242
type SchedulingResult struct {
43-
results map[string][]Endpoint
43+
results map[string][]Endpoint //nolint:unused
4444
}
4545

4646
// Scheduler is the implementation of a... scheduler.
@@ -51,7 +51,7 @@ type Scheduler interface {
5151
// - profiles - A subset of the registered scheduling profiles to be ran
5252
PreSchedule(request map[string]any, data scheduling.CycleState, results map[string][]Endpoint) map[string]SchedulingProfile
5353

54-
// PostSchedule recieves the output of the result(s) of the scheduling cycle(s)
54+
// PostSchedule receives the output of the result(s) of the scheduling cycle(s)
5555
// and makes sense of the data to be consumed by the calling system.
5656
// For example: suppose you have 2 profiles ShadowBoxing Profile & Production Profile.
5757
// PostSchedule would know to simply log the result of ShadowBoxing

0 commit comments

Comments
 (0)