Move settings scripts into sqlite DB #148
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backend refactor that is a prelude to other work in #126 - moving away from explicitly declared scripts in settings code and instead allowing users to attach a gcode script to any event that CPQ fires from the state machine.
This PR also tests (and fixes a couple inconsistencies) with
api.py
handlers - namely a new GETSTATE permission and actually using RMJOB perm.script_runner.py
to use DB queries instead of pulling from settingsscript_runner.py
unit testsplugin.py
driver.py
to use new script_runner methods, fix unit tests