Disable API Server recipes updates #382
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.
Pre-flight Checklist
Description of Change
Motivation and Context
As discussed in #314 and #224, and also in discord with @vraravam, this PR disables COMPLETELY the in-app recipes updates from the server.
I think this is the way to go to have a fully functional release soon, by making the app totally independent of the recipes on the server.
Ergo, for the user to get recipes updates, it needs to download a new Ferdium version, which will - after the first run of the new updated version - pop up the Reload Services message to update recipes to the newest version (bundled with the App).
DISCLAIMER: This can possible (not tested but most surely will) break the future of supporting custom recipes updates through a custom server - if users are using them to manage multiple account sync of custom recipes.
Screenshots
Please, look at the console:
Checklist
npm run prepare-code
)npm test
passesRelease Notes
Disable API Server recipes updates