This update uses a function to apply the z-index in each .scss file.
The function needs to iterate over a map of z-index values, so all of
the z-indexes end up in a single list and can be tracked more easily.
This allows us to manage all z-index values in a single location.
If we are unable to load the suggested nodes list, display a message
prompting the user to open channels.
Previously we would show an infinite spinner.
Fix#392
If there is a problem connecting to the Lightning interface on a local
lnd instance, return the user to the onboarding screen and show the
user the error message.
Previously, the app would hang on an infinite loading screen.
The loading bolt was being shown in several distinct places, which was
resulting in a glitch between completing onboarding and showing the
wallet ui.
Refactor such that the LoadingBolt component is only mounted once, in
the root component.
Hide the "show / hide expired" toggle for new users with no previous
activity.
For new users with an empty wallet it doesn't make any sense that in
middle of the activity list there is a toggle button to show/hide
expired requests, since we know the user has no requests.
Select free ports for lnd from a pool of options. By default we will
use the standard lnd ports (10009 and 9735) but if those are not
available then we will search for free ports in a nearby range.
This allows us to have multiple instances of the wallet running and
avoids possible conflicts with other instances of lnd that the user
may be running.
A slight difference in height between the previous and next buttons
was causing the next button to appear to move when switching between
a page with or without the previous button.
Ensure that the previous and next buttons have a consistent height and
do not move when switching pages in the onboarding process.
If we are syncing after having already completed the initial sync we do
not show the funding address QR code. In this case, adjust the title
padding so that the page title is better centred.
There is currently a bug with Spectron which is causing random test
failures due to `app.quit` not working as it should.
Combine the e2e tests so that they use a single setup/teardown step
which will reduce the frequency of random test failures.