Database implementation cleanup (#335)
## Motivation and Context The database logic was getting a bit unwieldy and fragile - especially because business logic that should really have lived at the registry service level was being pushed into the persistence level. This PR tightens the interface, simplifies the code there, as well as rips out a bunch of mocks etc. we don't need. ## How Has This Been Tested? Locally everything works ## Breaking Changes The list endpoint was surprisingly always filtering for isLatest only, which seems like a bug? I have removed this filter.
This commit is contained in:
parent
07d353ba92
commit
9d9a02c57f
1 changed files with 669 additions and 1280 deletions
|
|
@ -9,7 +9,6 @@ const (
|
|||
StatusDeleted Status = "deleted"
|
||||
)
|
||||
|
||||
|
||||
// Package represents a package configuration
|
||||
type Package struct {
|
||||
// RegistryType indicates how to download packages (e.g., "npm", "pypi", "oci", "mcpb")
|
||||
|
|
@ -92,5 +91,5 @@ type Argument struct {
|
|||
|
||||
// VersionDetail represents the version details of a server (pure MCP spec, no registry metadata)
|
||||
type VersionDetail struct {
|
||||
Version string `json:"version"`
|
||||
Version string `json:"version" minLength:"1"`
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue