michaaels commented on issue #9052: URL: https://github.com/apache/hop/issues/9052#issuecomment-6808242660
Hi @bamaer and @mattcasters, Yes, the connector’s existing responses can serve as a reference for defining the fields needed for the user and project use cases. Both areas are already implemented to a significant extent: - Hop users: plugin discovery, component configuration schemas through native metadata-injection APIs, and metadata type and object inspection. Responses include identifiers, names, descriptions, categories, property types, and allowed values where available. - Hop projects: project catalogs, pipeline/workflow inspection, component configuration, structural validation, dependencies, metadata references, and structural impact analysis. Responses also indicate incomplete or truncated results. We could use these responses to identify reusable fields, missing information, and the native Hop APIs behind each field. Some project information, such as its business purpose, main workflow, and intended test suite, would still need an explicit definition. The current structural lineage should also be distinguished from field-level lineage, which the connector does not guarantee. For Hop development, I suggest expanding the existing AGENTS.md with a module map, extension points, relevant APIs, and build/test guidance. General-purpose tools such as [Codebase Memory MCP](https://github.com/DeusData/codebase-memory-mcp) already provide repository indexing, symbol discovery, and relationship navigation for agents working with a source checkout. For the development use case, these general-purpose tools and expanded project guidance could complement Hop-specific harvesting. For the user and project use cases, the connector’s existing responses provide a concrete starting point for agreeing on the required fields and output format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
