FileSystemAPI events

[datashaman]

The FileSystemAPI events that are emitted when using the watch method are difficult to work with.

From experimentation this is the current flow:

• Create file emits rename

• Update file emits change

• Delete file emits rename

• Chmod file emits change

• Create dir emits rename

• Delete dir emits rename

• Chmod dir emits rename

Because the events are not very refined, it puts a lot of pressure on the event receiver to figure out what actually happened.
Each event would require a flurry of other calls to figure out if the file is still there, if the content changed or the mode, etc.

Expansion of the events to more accurately reflect what happened would be helpful and reduce a lot of code required in a client app.

[vadolasi]

It's actually quite complicated to work with these events.