fix: resolve golines formatting issues in provider test and config
Breaks down long lines in pkg/providers/anthropic_messages/provider_test.go and re-aligns struct tags in pkg/config/config.go to satisfy the golines linter which caused a CI failure. Co-authored-by: TanLuong <28281768+TanLuong@users.noreply.github.com>
This commit is contained in:
parent
aa2eac9741
commit
c80560348e
2 changed files with 9 additions and 5 deletions
|
|
@ -1048,10 +1048,10 @@ type SearXNGConfig struct {
|
||||||
}
|
}
|
||||||
|
|
||||||
type GLMSearchConfig struct {
|
type GLMSearchConfig struct {
|
||||||
Enabled bool `json:"enabled" env:"PICOCLAW_TOOLS_WEB_GLM_ENABLED"`
|
Enabled bool `json:"enabled" env:"PICOCLAW_TOOLS_WEB_GLM_ENABLED"`
|
||||||
apiKey string
|
apiKey string
|
||||||
secDirty bool
|
secDirty bool
|
||||||
BaseURL string `json:"base_url" env:"PICOCLAW_TOOLS_WEB_GLM_BASE_URL"`
|
BaseURL string `json:"base_url" env:"PICOCLAW_TOOLS_WEB_GLM_BASE_URL"`
|
||||||
// SearchEngine specifies the search backend: "search_std" (default),
|
// SearchEngine specifies the search backend: "search_std" (default),
|
||||||
// "search_pro", "search_pro_sogou", or "search_pro_quark".
|
// "search_pro", "search_pro_sogou", or "search_pro_quark".
|
||||||
SearchEngine string `json:"search_engine" env:"PICOCLAW_TOOLS_WEB_GLM_SEARCH_ENGINE"`
|
SearchEngine string `json:"search_engine" env:"PICOCLAW_TOOLS_WEB_GLM_SEARCH_ENGINE"`
|
||||||
|
|
|
||||||
|
|
@ -584,7 +584,11 @@ func TestBuildRequestBodyEdgeCases(t *testing.T) {
|
||||||
t.Fatalf("messages is not []any")
|
t.Fatalf("messages is not []any")
|
||||||
}
|
}
|
||||||
if len(messages) != 3 {
|
if len(messages) != 3 {
|
||||||
t.Fatalf("expected 3 API messages (user, assistant with text, assistant with tool_use), got %d: %#v", len(messages), messages)
|
t.Fatalf(
|
||||||
|
"expected 3 API messages (user, assistant with text, assistant with tool_use), got %d: %#v",
|
||||||
|
len(messages),
|
||||||
|
messages,
|
||||||
|
)
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
})
|
})
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue