Skip to content

Conversation

@tiginamaria
Copy link
Contributor

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@tiginamaria tiginamaria added the refactoring Making things better label Nov 3, 2025
@tiginamaria tiginamaria force-pushed the tigina/registry branch 2 times, most recently from a0a0e71 to 2c9eb29 Compare November 3, 2025 16:57
Add Feature interface
Make FeatureRegistry generic
Copy link
Contributor

@kpavlov kpavlov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM *Pair programming

@tiginamaria tiginamaria merged commit 913c0d1 into main Nov 3, 2025
4 checks passed
@tiginamaria tiginamaria deleted the tigina/registry branch November 3, 2025 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

refactoring Making things better

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants