File based nodes thoughts about pipeline-editor HOT 3 CLOSED

• We should validate that the file exists, how often? Do we need to watch the file somehow?

I would think when opening the file and on running / exporting? Also saving? I think that'd be enough

• Should we change the file label to just be the basename? xxx.ipynb feels a bit noisy...

I think there was some discussion about this recently - if I'm remembering correctly, it was the basename before we added the ability to run python nodes but we started using the full filename because there could be a python node and a notebook node with the same base name? Also because we could change the label of the node. However the nodes do have an icon to indicate the file type so I guess it's not really important for the first reason. @ptitzler I think I remember you bringing this up recently, what do you think?

• If a file is renamed should the node's file path also be updated?

Is there a straightforward way of finding the new filename? I think that'd be a good feature but I'm not sure how it'd be implemented

from pipeline-editor.

• We should validate that the file exists, how often? Do we need to watch the file somehow?

I would think when opening the file and on running / exporting? Also saving? I think that'd be enough

So, this should be part of the pipeline validation logic, so, whenever the validation occours.

from pipeline-editor.

Yea, I was assuming during validation was the bare minimum. I was more wondering if we should do any file watching for when required files are renamed/moved

from pipeline-editor.