puts the various ast perusers in their own folders
moves the 'parse' wrappers to their respective folders
redistributes responsibilities between extract-depencencies module and parser specific code
names things slightly more standardly, so it's easier to grok what happens (i.e. use parse when parsing things over various other terminology)
Unifying the 'per-parser' interfaces makes it more easy to add a new one/ or make it a plugin mechanism if necessary. Also, by setting up the interface we can introduce a mechanism to do other things with AST's, like providing information on the barelly-ness, LoC, NoS.
How Has This Been Tested?
[x] green ci
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Documentation only change
[x] Refactor (non-breaking change which fixes an issue without changing functionality)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist
[x] :book:
My change doesn't require a documentation update, or ...
it does and I have updated it
[x] :balance_scale:
The contribution will be subject to The MIT license, and I'm OK with that.
Description, Motivation and Context
Unifying the 'per-parser' interfaces makes it more easy to add a new one/ or make it a plugin mechanism if necessary. Also, by setting up the interface we can introduce a mechanism to do other things with AST's, like providing information on the barelly-ness, LoC, NoS.
How Has This Been Tested?
Types of changes
Checklist
[x] :book:
[x] :balance_scale: