MCP trace still uses light-class names for external calls and node className
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
Research direction
Open CallChainTracer.kt near line 185 and SpringMcpProvider.kt near line 1553. Replace direct light-class name usage with SourceNames.qualifiedNameOf or SourceNames.shortNameOf for external call targets and trace-node className. Verify that non-companion member trace output remains unchanged by running the relevant tests.
Written by the indexing model from the issue text.
Description
Component
MCP tools
Problem
On current public/main, CallChainTracer.kt:185 builds external-call targets directly from the light-class and JVM method names:
TracedCall("${receiverClass.name}.${callee.name}", ...)
For an external Kotlin class, this can expose JVM/light-class names such as Companion or $module instead of the source declaration name.
Also, SpringMcpProvider.kt:1553 builds trace-node className from the light class:
className = containingClass?.qualifiedName ?: containingClass?.name
Consequently, a companion member can still expose a class name containing ...Companion, even though PR #585 fixed the node methodName and call target/name paths that use SourceNames.
This is a code-reading finding, not a reproduced runtime run.
Expected
Trace external-call targets and trace-node className should use source-level names. Route both through SourceNames (qualifiedNameOf / shortNameOf) while keeping the trace output of non-companion members byte-identical.
Related
#571, #585, #568
- Dominant language
- Kotlin
- Stars
- 163
- Forks
- 16
- Avg merge
- 7h 4m
- Merged PRs (30d)
- 122
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from explyt/spring-plugin
-
in:spring-web
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
explyt/spring-plugin#576 ·
Maintainers usually reply within 1 day
-
in:spring-core native-link
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
explyt/spring-plugin#375 ·
Maintainers usually reply within 1 day
-
in:spring-core
Difficulty 4/5 3-5 days Newbie friendliness 48/100
explyt/spring-plugin#589 ·
Maintainers usually reply within 1 day
-
in:spring-data spring-mcp-tools
Difficulty 3/5 Half a day Newbie friendliness 70/100
explyt/spring-plugin#586 ·
Maintainers usually reply within 1 day
-
in:spring-web spring-mcp-tools
Difficulty 5/5 Over a week Newbie friendliness 25/100
explyt/spring-plugin#582 ·
Maintainers usually reply within 1 day
All issues in explyt/spring-plugin
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MetrolistGroup/Metrolist#4435 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
sk2andy/candy-browser#292 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Gallery#1167 ·
Maintainers usually reply within 1 day
-
[Bug]：自定义组件问题Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getActivity/AndroidProject#158 ·