Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fw upgrade one click #276

Closed

Conversation

germanferrero
Copy link
Contributor

This PR adds support for one-click installation in companion with libremesh/lime-packages#773

  • A banner is shown above the header saying that there is a new firmware version available when there is one.
  • New release section is added to firmware upgrade screen. In there, the user can trigger release downloading, and upgrading from it.

Also React Query is introduced to the code base. React query allows to separate server state handling logic from UI state. The best feature IMO being letting developers re-use server state data across components in a declarative way, without worrying about caching and de-duping.

By using react-query server state data is treated as such, decoupling it from global UI state given
by app context
@germanferrero
Copy link
Contributor Author

CI is failing at storybook build, because of a simple typo in the storybook repo, which will be solved when storybookjs/storybook#12883 gets merged.

Also, always try to login as root automatically before asking for password
@ilario
Copy link
Member

ilario commented Oct 25, 2020

Wow this is huge! Thanks @germanferrero!
Does this PR depend from libremesh/lime-packages#773 or can we merge this before merging libremesh/lime-packages#773?
Needless to say, as libremesh/lime-packages#763 and #275 are release blockers and this PR includes a patch, I would push towards merging this as soon as possible. @germanferrero @spiccinini do you think we can merge this already?

@germanferrero
Copy link
Contributor Author

@ilario I've opened #279 with the patch, so we do not depend on merging all this before. Sorry for the anti-pattern of coupling an urgent path with a new big feature.

Copy link
Contributor

@spiccinini spiccinini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested it and skimed through the code. It looks much more clear. Great work!

@germanferrero
Copy link
Contributor Author

I close this, since all changes were added by merging #278. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants