Closed prabhu closed 10 months ago
Added --remove-atom
as a CLI option to automatically remove the atom post creation in 1.7.0. This value is set to true for usages and parsedeps alone. Reworked the usages logic to reuse an existing atom that might be present.
This way when the user creates an empty atom or uses reachables or data-flow slicing the atom file would remain intact and reusable for usages slicing.
This would offer some speedup when dealing with large codebases. We need to find a better UX to communicate this since, otherwise, the user might be getting stale data.