search

iobroker-community-adapters / ioBroker.js2fs-community

replicate ioBroker scripts to files
MIT License
0 stars 3 forks source link

rename script in ioBroker Admin, old file still exist #14

Closed truegreyhound closed 4 years ago

truegreyhound commented 4 years ago

I renamed a script in the admin UI, then I had the new and the old script in the admin and in the file system. The renaming worked fine with some other scripts. Unfortunately I couldn't see any differences in my actions.

ioBroker.js-controller: 2.1.1 ioBroker.js2fs: 0.1.5 node.js: 10.17 OS: Win10 1909

Apollon77 commented 4 years ago

Do you have tried javascript 4.3 with mirroring functionality? Maybe we better drive this and phase out this adapter?

truegreyhound commented 4 years ago

script engine 4.3.4 Admin 3.7.2

Why phase out? What are the alternatives? You can deal with this mistake if you know it.

Apollon77 commented 4 years ago

As I wrote: the JavaScript adapter itself got a mirroring to filesystem Feature in 4.3.

We should try this ;-)

I personally also use js2fs but beside bugs like you found Lao object timestamps are not fully supported.

truegreyhound commented 4 years ago

okay, I will test. I only found it on the configuration page after you were informed again. Thank you

With VC I created a new file in a script subdirectory. The file was imported correctly by the Java script adapter into ioBroker as a type script.

Then I renamed the file in ioBroker UI. A short time later "the old file" was back. Certainly you the synchronization from the file system. Both files can also be seen in VC. After deleting the old file in ioBroker, everything is fine again.

I think that's due to the underlying mechanism and not a bug.

But how do you control that with the /// So that VC also finds this file. Are * .d.ts files excluded from synchronization? see #16

Apollon77 commented 4 years ago

Effects you described were with JavaScript adapter? Then ipen Issue there too?

truegreyhound commented 4 years ago

I will close the issue here, a corresponding issue already exists under JavaScript adapter #451