Closed HBaghdadi1995 closed 2 years ago
I do not see this in local testing. I assume this is because you called a function using a string rather than a character vector. Please can you provide an example to reproduce?
I do not see this in local testing. I assume this is because you called a function using a string rather than a character vector. Please can you provide an example to reproduce?
I assume this is because you called a function using a string rather than a character vector
That was it, my bad.
It happened when I called lumofile.merge_layout("C:\Users\Hasan\Downloads\Lumo_samples_M3\0.4.0.LUMO", "C:\Users\Hasan\AppData\Local\Gowerlabs\LUMO\coordinates_xxxxxxxx.json")
.
And it worked when I called lumofile.merge_layout('C:\Users\Hasan\Downloads\Lumo_samples_M3\0.4.0.LUMO', 'C:\Users\Hasan\AppData\Local\Gowerlabs\LUMO\coordinates_xxxxxxxx.json')
I've rewritten the issue and the comment, I'll have to check #24 incase it breaks character arrays.
It's ultimatley up to you to decide if we should accept both strings and character arrays, or only character arrays
It will break character arrays. The correct thing is to do some input validation and ensure that things are all character arrays at the user boundary.
Okay sure, I'll close this issue and the pr then.
Setup
Lumo v0.2.0
,Lumo v0.3.0
&Lumo v0.4.0
How to recreate
What Happens
lumo_merged_fn
is now generated as an array of strings, this is because[lf_name '_merged_' uid_name lf_ext]
in line 148, contains a mixture of strings and character vectors. Comparefullfile('foobar',['foo' 'bar'])
withfullfile('foobar',["foo" 'bar'])
as an example.Conclusion
This issue should be an easy fix, but there are multiple solutions around it.