Closed mbtools closed 1 year ago
I knew it would come one day ... I started feeling that ajson becomes a bit bloated.
First thoughts:
Just thoughts. No immediate solution.
any impact on existing projects if split the package into 3 subpackages (in one repo)? core, utils and perf (for perf test prog) ?
abapGit impact: might need some adjustments in the renaming, but no problem, go for it
anyhow, we will get tree-shaking sometime for ABAP, abaplint ftw
OK, so the first step would be this: #152 Have a look, if looks fine, I'll merge
The split into core and others looks good. Thanks!
I have several projects where I want to include the core ajson functionality (no filter, no mapping). However, now it's all linked with dependencies, so I need to copy 3 classes + 4 interfaces + exception. Ideally, it should be 1 class, 1 interface, 1 exception.
I can, of course, clone and reduce this myself in another repo (with credit to you). But I wonder if there's a way to manage this in your repo without causing double maintenance. It needs an abapmerge for OO... Anyway, just something to think about.