Link.Export should call beforeWrite [for variables]

[lstefano71]

UCMD.Export (

link/UCMD.dyalog

Line 313 in cca5c7a

Export←{ ⍝ Write items to file in folders

) ignores completely objects of nameclass 2. This means that when the namespace is first exported, variables aren't allowed a chance to be processed by onWrite. Is this by design or is it an oversight?
In fact: shouldn't Export always use onWrite if present before commiting to the various []NPUT? If not, it's possible that special logic in onWrite only kicks in when the objects (even classes 3, 4 and 9) are modified after the first export. But the logic in onRead/onWrite could prescribe for certain objects different extensions, different encodings. And this would mean a big mess in the source folder...

[mkromberg]

Link.Export should probably call beforeWrite for ALL write operations. Support for variables using .apla (array format) is planned - see issue #37. Some kind of switch will be provided to say whether Link.Export should include variables.

[e9gille]

Yes, Export should allow writing out existing arrays but please don't make it a default. It should be something you ask for explicitly using a switch.

[nicolas-dyalog]

fixed in link v2.1