* Upgrade commander to 7.0.0
* Add url to Api call
This is needed to allow access to sends that are available from a
different Bitwarden server than configured for the CLI
* Allow upload of send files from CLI
* Allow send search by accessId
* Utils methods used in Send CLI implementation
* Revert adding string type to encrypted file data
* linter fixes
* Add Buffer to ArrayBuffer used in CLI send implementation
* update package http-proxy-agent
* Update syntax appropriately
* Explicitly add utils package to fix broken tests
* Revert "Explicitly add utils package to fix broken tests"
This reverts commit 2cf03fdcbae89e55124c7e36201238520434f8cc.
* Import util in spec to make sure it gets bundled
* Revert "Import util in spec to make sure it gets bundled"
This reverts commit 79264cdab0ef37af855d64a6dc3ef574575309d2.
* Add alias to ensure util module resolves in tests
Co-authored-by: Thomas Rittson <trittson@bitwarden.com>
* Do not export trashed items
* Test Item exporting
Does not test organization export. Export's use of apiService is not
very testable. We will either need a testApiService or to refactor
apiService to make mocking easier.
* Linter fixes
It is not possible to edit and share at the same time. Browser extension
currently utilizes this layout and it is confusing. This change is in
conjunction with altering that UI.
* Use logService for console messages
* Implement a base ConsoleLog service
Use this class as a default for other services that would like to output
to console. This service is overriden in CLI and Desktop to use CLI's
consoleLogService and electronLogService, respectively.
* Use browser-process-hrtime for timing
* test LogService implementations
* Ignore default import of hrtime
* Clean up imports. Require ConsoleLog injection
Co-authored-by: Matt Gibson <mdgibson@Matts-MBP.lan>
* Change cipher type based on csv type header
* Test identity and credit card import
* Do not use node 'fs' module
Karma is being used for automated tests so node modules are not available
* WIP: mac and windows 1password importer split
Need to improve windows field identification to limit secret data
exposure and improve user experience
* Hide fields with likely secret values
Co-authored-by: Matt Gibson <mdgibson@Matts-MBP.lan>
* Initial commit of personal ownership enforcement
* Updated policy type enum
* Sync'd eventType for Policy_Updated with server enum value
* Added policyId to eventResponse model
* Removed explicit typing
* Use logService for console messages
* linter autofixes
* Use full import path
* Implement a base ConsoleLog service
Use this class as a default for other services that would like to output
to console. This service is overriden in CLI and Desktop to use CLI's
consoleLogService and electronLogService, respectively.
* linter fixes
Co-authored-by: Matt Gibson <mdgibson@Matts-MBP.lan>
* Fix import of 1password csv
* 1password is using '\' as a quote escape character.
* 1password's csv headers are sometimes capitalized. We want to identify
them case insensitively
* Change cipher type based on csv type header
* Translate 1password data to correct fields
* Test identity and credit card import
* linter fixes
* Do not use node 'fs' module
Karma is being used for automated tests so node modules are not available
Co-authored-by: Matt Gibson <mdgibson@Matts-MBP.lan>
* Add context menu on right click to mac
* Add hide dock setting
* Change "hide dock" to "always show dock"
* Add support on mac for minimize to menu bar on close, minimize or start
* Add "openAtLogin" to ElectronConstants
* Add "restoreFromTray" to TrayMainService
* support for encrypted json export
* adjust filename prefix for encrypted formats
* flip if logic
* remove format param from encrypted export
* encryptedFormat getter
The motivation for this is https://github.com/bitwarden/cli/issues/129
where failed sync's are swallowed by try-catch. By moving the try-catch
to the outside it is possible to reuse the already existing
allowThrowOnError argument which callers can use to signal whether
fullSync should throw or ignore errors silently. This patch is
companioned with a patch to the SyncCommand CLI command to pass
allowThrowOnError.
This is in conjunction with API changes that validates the last known
revision date provided here with the actual last revision date on the
server to block potential data loss due to client desyncs.
Co-authored-by: Matt Gibson <mdgibson@Matts-MBP.lan>
