When we start up the app we attempt to fetch the users store settings
from IndexedDb by loading up a hidden browser window and execute
code within it to connect to and fetch settings from the database.
This fix ensures that we properly close out this hidden window once we
have fetched the user settings. This resolves an issue that prevented
the production build from starting up fully.
Refactor Containers and Routes in order to make the code a little more
readable, reduce duplication, and prepare the codebase for integration
of the new Home screen.
- Break out the Root container into several smaller containers that are
responsible for connecting themselves to the Redux store.
- Use routing for navigation between primary containers
- Unbundle the `Syncing` Component from the Onboarding section and hook
up to router so that it can be access by navigating to `/syncing' (we
want to be able to load existing wallets and initiate syncing outside of
the context of the onboarding process)
- Reduce code duplication
- Create `TitleBar` component and implement once at the top level
- Create `withLoading` HOC and use to display the loading screen when
needed.
In some languages like german, the order of the words was wrong and could not be fixed within crowdin.
revert message keys
- revert message keys
- correct translation for existing translations
Several of our elements were missing z-index property, causing them to
display incorrectly in the app.
Ensure that we import styles/variables.scss before attempting to use
the z() helper function that it provides.
By not loading locale data into the main process we can considerably
reduce it's size. We the only thing we need access to in the main
process is the translation sets (used for the languages menu).
refactor the i18n code so that the locale data can only be loaded when
needed (in the renderer).
Thew latest version of yarn includes a new integrity field for all
package entries.
Regenerate our yarn.lock files so that they are fully updated to the
latest file format.
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.