Uh oh!
There was an error while loading. Please reload this page.
v1.4.1 #254
v1.4.1
#254
Replies: 0 comments
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
CLDK python-sdk v1.4.1
A patch release with three bug fixes that make entity lookups truthful across the language backends. No breaking changes — drop-in upgrade.
🐛 Fixes
Module-level functions are now resolvable through
get_method— and callers/callees stop lying about them (Python & TypeScript). Previouslyget_methodsearched class scope only, so module-level functions (most Python code, and the dominant callable kind in TypeScript) were unreachable — andget_all_callers/get_all_calleessilently returned an empty result for them even when the call graph contained the edges. The scope argument now accepts a module name as well as a qualified class name, and callers, callees, parameter and comment lookups all inherit the fix, on both the local and Neo4j backends. (#250, #251)Java lookups no longer crash on a miss. Looking up an unknown class or method signature used to raise
AttributeErrorfrom deep inside the SDK (get_method_parameters), because lookups silently returnedNoneunder non-Optional type annotations.get_method/get_class/get_java_fileare now honestly annotated as returningNoneon a miss — on the ABC, both backends, and the public facade —get_method_parametersreturns an empty list, and all internal call-graph and comment lookups are guarded. Behavior on successful lookups is unchanged. (#252)Upgrade
Full details: CHANGELOG · GitHub release
All reactions