dc@4gl.io d626cb8f2d fix(makedata): read KEEPME from every input row, and keep it out of the Viya seed ...

The KEEPME probe did 'set work.fromjs' inside the varnum guard and then stopped,
so only the first observation was inspected: a submission that set KEEPME on a
later row still self-destructed.  It now reads to end of file.

makeDataNextViya.json ships KEEPME=Y and is the config that seeds a real Viya
environment, so the default posture there was 'the seeding program stays on the
server'.  KEEPME stays in makeDataSas719.json, which exists for the test
harness, and is removed from the environment seed.

2026-10-27 14:49:59 +00:00

..

configNextViya.json

fix: agent skills and nextviya deploys

2026-08-19 17:17:30 +01:00

contextConfigCreate.json

init

2023-07-13 13:44:05 +02:00

contextConfigCreateProduction.json

init

2023-07-13 13:44:05 +02:00

contextConfigEdit.json

init

2023-07-13 13:44:05 +02:00

contextConfigEditProduction.json

init

2023-07-13 13:44:05 +02:00

makeData4GL.json

feat: validation on RLS for REPLACE, + docs + tests. Closes #211

2026-07-22 19:01:21 +01:00

makeDataNextViya.json

fix(makedata): read KEEPME from every input row, and keep it out of the Viya seed

2026-10-27 14:49:59 +00:00

makeDataSas9.json

init

2023-07-13 13:44:05 +02:00

makeDataSas719.json

test(hooks): seed the baseline from an npm script, not from testsetup

2026-10-26 23:51:59 +00:00

makeDataServer.json

feat: validation on RLS for REPLACE, + docs + tests. Closes #211

2026-07-22 19:01:21 +01:00

makeDataV4.json

init

2023-07-13 13:44:05 +02:00

makeDataViya.json

init

2023-07-13 13:44:05 +02:00

requestConfig.json

init

2023-07-13 13:44:05 +02:00

requestData.json

init

2023-07-13 13:44:05 +02:00

requestDataProduction.json

init

2023-07-13 13:44:05 +02:00