Marc Bernard

👍

```abap FIND REGEX '(\d\d).*(\d*)' IN `123` SUBMATCHES DATA(p1) DATA(p2). ``` p1 = '12'. p2 = '3'. https://regex101.com/r/SMEF5o/1 '12', null https://regex101.com/r/JAjp0V/1 '12', '3'

FALV doesn't use APACK. The issue is with abapGit generating the ZIF interface... Yet another reason to find a replacement for APACK (working on it)

Thanks for the test

it will take care of itself when Alexander's AJSON is updated and mirrored back into abapGit

if you keep data and structure separate, you will have to deal with potential mismatches (like new or removed fields in table). the point of system tables is the opposite:...

We already have part of the general solution in ZCL_ABAPGIT_OBJECTS_GENERIC (based on tables in OBJSL mapped to R3TR TABU entries).

Something to keep the discussion going... Proposal for /data/data.json ``` { "data" : [ // Minimal case (mandatory spec) { "type": "TABU", // "CDAT", "TDAT", "VDAT", ... "name": "ZTABLE", "format":...

The data might be produced outside of SAP, for example a csv file with geo-codes, and uploaded to the repo. I think it's better to keep the definition of what...

i would keep {object}.{type}.json for the definition files to stay consistent with other AG files. Then add "filename" to the header spec so the data file can be anything. It...