API proposal: plugin actions

[Derkades]

API proposal: plugin actions

[partydragen]

Yea then its the question we discussed before to use Queue system as it kinda belongs in there, But at the same time it don't and might be better with a own system for that idk

Also by type wont that be messy as then you need to check if its a command to avoid hard coding each type so you don't need to add support for new modules like

• store:command
• forms:command
• trophies:command

unless you check after : is "command" idk

[samerton]

Something to consider with this approach would be how we store these "actions" that haven't been synced yet, and also how we know if we should store them or not (i.e. if there is no plugin set up storing them would be pointless)

[Derkades]

Also by type wont that be messy as then you need to check if its a command to avoid hard coding each type so you don't need to add support for new modules like
* store:command
* forms:command
* trophies:command

We could add a generic type for command, good idea.

Something to consider with this approach would be how we store these "actions" that haven't been synced yet, and also how we know if we should store them or not (i.e. if there is no plugin set up storing them would be pointless)

I assumed we'd just store it in a database table. You do make a good point about actions piling up when no plugin is set up. Perhaps pending actions should be removed after a certain timeout, like a month?

[partydragen]

Something to consider with this approach would be how we store these "actions" that haven't been synced yet, and also how we know if we should store them or not (i.e. if there is no plugin set up storing them would be pointless)

Could add last ping colum to servers table like i do with Store connections, Then we know if server is setup correctly and we know its active or not