An export which fails because it requires caseCode still creates a directory

Dyalog / link

Source code for Link – the built-in component that enables the use of text files as the primary storage mechanism for APL source code

https://dyalog.github.io/link

MIT License

19 stars 10 forks source link

An export which fails because it requires caseCode still creates a directory #497

Open mkromberg opened 1 year ago

mkromberg commented 1 year ago

A ]Link.Export which fails because it requires caseCode=1 to succeed, still creates an empty target directory. The same may be true of other export failures.

ghost commented 1 year ago

In ⎕SE.Link.Test:

⍝assert'~⎕NEXISTS folder'        ⍝ folder must not exist
assert'0∊⍴⊃⎕NINFO⍠1⊢folder,''/*'''  ⍝ folder must remain empty

At some point it was decided the folder involved should stick around. (See also #113)

mkromberg commented 1 year ago

I am not sure there is enough evidence to say that "it was decided", this may just have been a change made in order to keep the QAs running after making other fixes which resulted in the folder being left behind. I cannot see any reason why you would want the folder to be there after a failed export, it makes no sense.