Server Side Actions

[worksofliam]

It'd be cool if we had server side actions, which means instead of storing an action on the client, we store it (and edit it) on the server so all users can have access to it.

Things to determine: where do we store this data?

• Do we store it in the database?
  • Yes because it the risk of data being overwritten is low
• Do we store it in a JSON file in the IFS?
  • Yes because the JSON is easier to manipulate if we want to add more data
  • Perhaps we can automatically manage it as a git for our server files

There are probably more reasons, but this would be a killer feature.

Server side actions would only work for member, streamfile and object types not [local] file.

[SJLennon]

While this is being discussed, here's another thought.

I've wondered about whether actions should be segregated into user provided actions and system provided actions, with user actions taking precedence. System provided actions could be refreshed at any time as new features are added but this would not alter any existing user actions. As far as I know there is currently no way to pick up new actions, other than creating a new connection or editing settings.json.

Possibly the extension has matured enough that new actions will be fairly infrequent.