[Backend] Expose procedures as entities #426
No reviewers
Labels
No labels
architecture
authentication
backend
bug
ci/cd
cleanup
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
media
mobile
new feature
notes
packaging
question
ui
upstream breaking change
voice
waiting user input
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
platypush/platypush!426
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "341/procedure-entities"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
See #341
procedureentities architecture. 06781cd72cconfig.get_config_dirmethod. ffc3fe218dactionsfor YAML procedures.ProcedureTypeenum. e593264eabprocedures.saveandprocedures.deleteactions.dbconf.PRAGMA foreign_keys = ONon SQLite connections. 7cc7009d08is_definedmacro for system plugin entities. 9d086a4a10proceduresfeatures.proceduresplugin.[Backend] Expose procedures as entitiesto WIP: [Backend] Expose procedures as entitiesprocedures.save.github-mirrorscript.procedures.to_yamlaction.procedures.to_yaml. f18d0d8b74actionsfield inprocedures.save.actionorname. 5a7068501aidfield inProcedure.build. 946c7b1783This enables constructs like this in procedures: ```yaml - return - return 1 - return: ${output} ```ifqueue flushing logic.procedure._serialize_actionshould also support strings.- Add `set` statement, which can be used to set context variables within YAML procedures. Example: ```yaml procedure.test: - set: foo: bar - action: logger.info args: msg: ${bar} ``` - More reliable flow control for nested break/continue/return. - Propagate changes to context variables also to upstream procedures.WIP: [Backend] Expose procedures as entitiesto [Backend] Expose procedures as entities