[plugin] Logic to migrate legacy settings and barebones wizard#5445
Merged
[plugin] Logic to migrate legacy settings and barebones wizard#5445
Conversation
Got lost in conflict resolution
Including changes to conform
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Some logic to identify legacy configurations and import them into OctoPrint-managed settings, along with a basic wizard for doing that.
The wizard UI will be cleaned up later, along with additing additional functionality related to enabling autolaunch and other setup.
Additionally, this changes the eslint config to accomodate JavaScript on the OctoPrint side.
See #4927 for more context related to the plugin effort.