Skip to content

Feature implementation from commits 0d15607..701988f#4

Open
codeOwlAI wants to merge 15 commits intofeature-base-branch-4from
feature-head-branch-4
Open

Feature implementation from commits 0d15607..701988f#4
codeOwlAI wants to merge 15 commits intofeature-base-branch-4from
feature-head-branch-4

Conversation

@codeOwlAI
Copy link
Owner

@codeOwlAI codeOwlAI commented Jun 30, 2025

PR Summary

Data Model Refactoring: Entry to Server Type Transition

Overview

This PR implements a fundamental data model restructuring, replacing the Entry type with Server type throughout the codebase, including database interfaces, service layers, and core model definitions.

Change Types

Type Description
Refactor Major restructuring of Go API schema definitions
Breaking Complete modification of data model hierarchy and service interfaces

Affected Modules

Module / File Change Description
database/mongo.go Changed the type of 'results' variable from []*model.Entry to []*model.Server in MongoDB List function
model/model.go Complete overhaul of schema definitions including removal of struct types, addition of new ones, and transition from JSON-only to JSON+BSON tags
service/fake_service.go Changed return type of fakeRegistryService.List method from []model.Entry to []model.Server

Breaking Changes

  • All code depending on model.Entry type will need to be updated to use model.Server
  • Data model hierarchy has been significantly altered
  • Service interfaces now return different types
  • Database operations now work with different data structures

Notes for Reviewers

  • Verify that all references to the old data types have been updated consistently
  • Check for any potential data migration concerns with the schema changes
  • Ensure BSON tags are properly aligned with existing MongoDB collections

connor4312 and others added 15 commits May 13, 2025 14:55
* Update the model to handle new changes to schema based on modelcontextprotocol#33

* Made the import script a little simpler.
* Add a new updated seed file
* update template mcp.json file for publisher
I originally introduced `package_canonical` into the API schema because,
at the time, we were thinking to "pin" the version of the MCP server to
_one_ of the referenced source code packages.

We are no longer doing this (we are maintaining a separate notion of
`version` unique to the MCP server), so I don't believe
`package_canonical` is needed anymore. Does anyone see otherwise?

This change removes all mentions in READMEs and usages in code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants