There is a bug in CodeGraph. The Rust engine version in CodeGraph v1.5.0 has an issue. When using codegraph-win32-x64\codegraph\bin\codegraph callees + to extract java methon downstream call chains, if a callee method in the current method's sub‑chain belongs to a third‑party JAR, the tool skips it by default and then substitutes another method with the same name from the project source code. This is a serious problem and is unreasonable. If a third‑party dependency prevents proper linkage extraction, the tool should fall back to terminating the current chain (i.e., keep the call as a leaf node) rather than injecting an incorrect replacement. Is there a fix planned for this? Alternatively, is there any other configuration option (like "keep_unresolved_callees": true) that can work around this issue?
There is a bug in CodeGraph. The Rust engine version in CodeGraph v1.5.0 has an issue. When using codegraph-win32-x64\codegraph\bin\codegraph callees + to extract java methon downstream call chains, if a callee method in the current method's sub‑chain belongs to a third‑party JAR, the tool skips it by default and then substitutes another method with the same name from the project source code. This is a serious problem and is unreasonable. If a third‑party dependency prevents proper linkage extraction, the tool should fall back to terminating the current chain (i.e., keep the call as a leaf node) rather than injecting an incorrect replacement. Is there a fix planned for this? Alternatively, is there any other configuration option (like "keep_unresolved_callees": true) that can work around this issue?