gpgme/lang/js/unittest_inputvalues.js, branch gpgme-2-baseGnuPG Made Easy.http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-2-base2018-08-20T13:12:01Zjs: add and apply eslint rules2018-08-20T13:12:01ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-20T13:12:01Zurn:sha1:dd32daad0bb21e3d5567326d0b2e548ff8510431
--
* mainly spacing, see .eslintrc.json for details
js: change the write access for js class methods2018-07-27T18:36:21ZMaximilian Krambachmaximilian.krambach@intevation.de2018-07-27T18:36:21Zurn:sha1:94ee0988d4eaac27785de6efb7c19ca9976e1e9c
--
* src/ [Connection, Error, Key, Keyring, MEssage, Signature, gpgmejs]:
Functions and values that are not meant to be overwritten are now
moved into their constructors, thus eliminating the possibility of
overwrites after initialization.
* Key: The mode of use (synchronous cached, or async promises) ivs now
determined at initialization of that Key. The property Key.isAsync
reflects this state.
* unittests: fixed old Key syntax for testing.
* Message.js isComplete is now a method and not a getter anymore.
* Added some startup tests.
js: implement import/delete Key, some fixes2018-06-06T09:57:41ZMaximilian Krambachmaximilian.krambach@intevation.de2018-06-06T09:57:41Zurn:sha1:0356a667c5a8b4fdb4404cebb57475ed3f39ade9
--
* Keyring.js
- implemented importKey: importing one or more armored public key
blocks.
- implemented deleteKey: deleting a public Key from gpg.
* Key.js renamed property Key.armor to Key.armored
* Helpers.js: toKeyIDArray does not complain anymore if there are no
keys. Not having Keys in e.g. signing keys in encrypt is legitimate
and common, the complaints were getting spammy
* Errors.js: gpgme_errors now always pass an optional additional
message, for easier debugging in minified code
* Connection.js: Fix in gpgme-json responses containing objects
* eslintrc.json: Start using eslint. A cleanup to conform to it is not
done yet
* Added further tests for the new functionality
js: Keyring listing keys2018-05-28T15:26:56ZMaximilian Krambachmaximilian.krambach@intevation.de2018-05-28T15:26:56Zurn:sha1:53ce2b94bc35243710dec9b7972c7aaaa79dbc75
--
* implementing Keyring methods:
- Keyring.getKeys: has an additional option that retrieves the armor
and secret state once at the beginning. This is power hungry, but
allows for Keys to be used directly (without querying gpgme-json
each call)
* permittedOperations.js: reflect recent changes in the native
counterpart, adding more options
* Key: adding two methods for retrieving the armored Key block and
for finding out if the Key includes a secret subkey.
js: implement Key handling (1)2018-05-25T17:02:18ZMaximilian Krambachmaximilian.krambach@intevation.de2018-05-25T17:02:18Zurn:sha1:7a73d88aba106d571f121dc3230864c81a76e5db
--
* Keys can now be queried for information. Onne version queries gnug
directly (asynchronous Promise in javascript terms), the cached
version refreshes on demand.
* Small fixes:
src/Connection.js joins answers that stay json properly now
js: Added browser testing for unit tests2018-05-03T16:03:22ZMaximilian Krambachmaximilian.krambach@intevation.de2018-05-03T16:03:22Zurn:sha1:c755287ba845c4cbbf1d50e5aafecb2e687c7ac9
--
* Added unittests to be run inside a Browser. To be able to access
the non-exposed functions and classes, a testing bundle will be
created, containing the tests (unittests.js) and the items to be
tested.
* src/Helpelpers, src/Key, src/Keyring: fixed some errors found
during testing.