* Add per-key data limits to the UI
* Hold byte values instead of DisplayDataAmounts in OutlineServerView and OutlinePerKeyDatALimitDialog
This allows us to fix a layering issue where, at the time of converting
a server access key to a DisplayAccessKey, we couldn't compute the
'relevant transfer' for progress bar displays since we couldn't get at
the server's default data limit.
* Mayp#values() returns an Iterator, not an array
* Rename event field to defaultDataLimitBytes
* Don't reset the dialog state on failure
* Use a loop instead of Math.max in refreshTransferStats
* Unconditionally enable the default data limit in the UI after adding it to the server
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
* Consistent handling of the view's default data limit state for both addition and removal
* Use callbacks to set and remove the per key data limit
* s/_showMenu/_showDataLimit/g
* Make language a public property of the dialog
* The dialog only needs the active data limit
* Use a separate method for the handler to open the dialog
* Use _activeDataLimitBytes
* We can use the ?? operator in `refreshTransferStats`
* s/dataLimitType/dataLimitUnit/g
* Rename a couple members
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
Running "shellcheck", and attempting to comply with the shell script
style guide, required hundreds of trivial changes, and a small number of
nontrivial ones. For ease of review, this PR includes only the
nontrivial changes.
* Internationalize data transfer amounts
* Internationalize units and currency
This required updating to Typescript 4 and adding compiler changes for the server manager in order to support newer features of `Intl`.
This change also fixes it so that the server city, creation date, and data limits no longer are stuck to the old language ater changing languages.
* Remove stray log
* Respond to review comments
* Remove byte-size
* Move to `web_app`
This code is only intended to be run in a web environment, not in Node.
* Respond to review comments
* Use property binding to the app language
* Respond to review comments
* Respond to review comments
* s/get/format
* Error out on Node
* Set the persisted app language before starting the app to prevent issues with undefined language at startup
* Respond to review comments and broaden covered languages
* Ensure that Karma and Electron use the same Chromium version
* Move the unit test to server_manager. This fixes an error on Travis involving importing from a package.json governed by a different tsconfig
* Unconditionally build the install script in the web app test
* Moves server progress view to outline-server-view
* Stops progress view animation; small refactor
* Auto-format
* Updates app tests
* Addresses review comments
* Addresses review comments
* Addresses review comments
* Addresses review comments
* Explicitly renders the server view dom-repeat to ensure view is added to the DOM
* Makes showServer synchronous