Update get entrypoint classes and methods #85
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
We had a number of problems with singleton classes for entrypoint detection. So we moved the logic to codeanalyzer-java v2.1.0 and CLDK just uses the data model to decipher if the class or method is an entrypoint.
How Has This Been Tested?
Added 2 test cases in
tests/analysis/java/test_jcodeanalyzer.py
:These can be run with
pytest --pspec --cov=cldk --disable-warnings tests/analysis/java/test_jcodeanalyzer.py -k "test_get_all_entrypoint_methods_in_application or test_get_all_entrypoint_classes_in_the_application" -s
Breaking Changes
No
Types of changes
Checklist
Additional context
pyproject.toml
so that the test cases run.find_libclang()
so that the lookup forlibclang.so
works: