* Format the fieldvalue as a LocaleDateString instead of epoch when importing a date from 1P
This would be better solved by storing it as a date FieldType instead of Text. But since it is unclear when new field types are added, this solution serves as a fix for now and also guides the solution when new fieldtype exists.
* Remove trailing whitespace
* Add tests for custom fields of 1pif imported identity
* Change representation of 1pif imported dates to UTC string
* Changes after running prettier
Co-authored-by: Daniel James Smith <djsmith@web.de>
* 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>
* allow base importer to receive custom field type
* 1password importer uses hidden field type
for custom fields marked as 'concealed'
* 1password 1pif importer specs
* remove 'focus' from specs
* change field type logic into simple one liner
