split OverridingJavaClassSource into two subclasses

[SamarthBengle]

No description provided.

[swissiety]

please clean up the old/existing class - is that deletedMethods etc. newly introduced logic?

[swissiety]

an equivalent construct already exists in..Position?

[SamarthBengle]

I didn't find anything suitable for it. So I used like this

[codecov]

Codecov Report

❌ Patch coverage is 0% with 335 lines in your changes missing coverage. Please review.
✅ Project coverage is 70.25%. Comparing base (609abf8) to head (2c47939).
⚠️ Report is 215 commits behind head on develop.

Additional details and impacted files

@@              Coverage Diff              @@
##             develop    #1361      +/-   ##
=============================================
- Coverage      71.52%   70.25%   -1.28%     
  Complexity        32       32              
=============================================
  Files            446      448       +2     
  Lines          18514    18849     +335     
  Branches        2964     2988      +24     
=============================================
  Hits           13243    13243              
- Misses          4159     4494     +335     
  Partials        1112     1112              

Components	Coverage Δ
core	64.84% <ø> (ø)
java.core	60.31% <0.00%> (-12.19%)	⬇️
java.bytecode.frontend	79.68% <ø> (ø)
jimple.frontend	74.25% <ø> (ø)
apk.frontend	73.26% <ø> (ø)
interceptors	77.17% <ø> (ø)
callgraph	84.83% <ø> (ø)
codepropertygraph	75.12% <ø> (ø)
analysis.intraprocedural	66.24% <ø> (ø)
analysis.interprocedural	67.66% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[SamarthBengle]

please clean up the old/existing class - is that deletedMethods etc. newly introduced logic?
Yes, this is new. I added it to avoid copying entire collections when deleting, it just marks what to hide instead

[swissiety]

please clean up the old/existing class - is that deletedMethods etc. newly introduced logic?
Yes, this is new. I added it to avoid copying entire collections when deleting, it just marks what to hide instead

please don't - I see the thought of doing it on-demand as well but we have to recalculate the collection(s) on every call while the collections are expected to be "small" so it just adds more logic