You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Was testing the new version before trying to update. Noticed that when you define a new custom folder. it will change the foldername to uppercase.
It can probably be fixed by changing in the config.json file itself directly as a workaround. But I haven't tried since its just a test environment. As I have modified some things in the previous version that made me want to test before actualyl updating.
Lumerica
changed the title
[Bug]: The new method to create customd default sub folders creates changes your custom folder uppercase
[Bug]: The new method to create custom default sub-folders changes the custom folder to uppercase
Oct 29, 2024
Describe the bug.
Was testing the new version before trying to update. Noticed that when you define a new custom folder. it will change the foldername to uppercase.
It can probably be fixed by changing in the config.json file itself directly as a workaround. But I haven't tried since its just a test environment. As I have modified some things in the previous version that made me want to test before actualyl updating.
Steps to reproduce the problem.
Expected behavior
Same characters shown, same upper/lower case
System info
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: