Repository navigation
Replies: 3 comments
|
Thank you for describing the framework-fork use case. You can index the application and framework separately and query each by project name. There is also |
|
Thank you again for the framework-fork use case. Checking back: which language and one application-to-framework call should be connected? Discussion #2500 now provides a concrete, separate service/GraphQL example; that helps distinguish its declared-link proposal from the arbitrary library-fork navigation requested here. There is no new general cross-project resolution claim to make from this thread. |
|
Thank you again for the discussion. If general application-to-framework navigation is still needed, please share the language and one expected cross-project call. |
Uh oh!
There was an error while loading. Please reload this page.
It would be great if there was a way to somehow link projects together. For example, I'm writing a project and next to it I have forks of frameworks and libraries that I use. And so that the MCP could go into the framework itself and somehow analyze the code that is needed for the agent.
All reactions