feat!: refactor tool discovery into extensible parser registry pattern #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement Parser Registry Pattern to enable support for multiple API specification formats beyond OpenAPI. This creates a clean, extensible architecture for future Postman Collections, GraphQL, and other formats.
Changes:
APISpecParserabstract base classParserRegistryfor parser management and discoveryOpenAPIParserclassOCPSchemaDiscoveryto orchestration layer using registryBREAKING CHANGE: Private methods moved from
OCPSchemaDiscoverytoOpenAPIParserclass. Methods like_parse_openapi_spec(),_normalize_tool_name(),_filter_tools_by_resources(), and others are no longer accessible onOCPSchemaDiscovery. Code using these private methods should use theOpenAPIParserclass directly or the publicdiscover_api()method.