Open JonasHelming opened 3 years ago
Should we not also move the updater to the Theia repo, @JonasHelming?
Yes, mid term this would probably make sense.
We are free to move code around within the project, so it's totally up-to us.
Should we not also move the updater to the Theia repo, @JonasHelming?
Before we think about moving, we should consider the following:
readme
to properly describe this extension (like other extensions).example-electron
(even manually). Does this extension provide any functionality that can be easily tested with example-electron
or is it only useful for packaged electron applications?From my initial newbie look at theia-updater one may want to consider breaking out the url/directory strings in theia-updater-impl.ts into something configurable.
From my initial newbie look at theia-updater one may want to consider breaking out the url/directory strings in theia-updater-impl.ts into something configurable.
This would make sense and we would accept a PR, currently we have no plans to make the updater more generic, therefore we put it in the Backlog milestone some time ago.
After splitting the updater from the rpdocut branding (https://github.com/eclipse-theia/theia-blueprint/pull/43) we should consider renaming the updater extension. It is actually generic, so it could potentially be reused by any other application relying on the electron updater.