diff options
| author | Maximilian Krambach <[email protected]> | 2018-07-31 15:35:52 +0000 |
|---|---|---|
| committer | Maximilian Krambach <[email protected]> | 2018-07-31 15:35:52 +0000 |
| commit | 6313a2de9ee84a9321292f775e4d6c790486d3dc (patch) | |
| tree | a6c1578d0162ea37e3a41025a0ef655684121098 /lang/js | |
| parent | js: Fix Key.hasSecret answer (diff) | |
| download | gpgme-6313a2de9ee84a9321292f775e4d6c790486d3dc.tar.gz gpgme-6313a2de9ee84a9321292f775e4d6c790486d3dc.zip | |
js: fix confusion about loop in last commit
--
* The aim is to iterate through the results of the first request
(all keys), and then add the propert 'hasSecret' to those that
are in the second request (secret Keysring) as well. I messed
this up in a recent change, and it escaped testing.
Diffstat (limited to 'lang/js')
| -rw-r--r-- | lang/js/src/Keyring.js | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/lang/js/src/Keyring.js b/lang/js/src/Keyring.js index 8715a47d..d25216c6 100644 --- a/lang/js/src/Keyring.js +++ b/lang/js/src/Keyring.js @@ -79,9 +79,8 @@ export class GPGME_Keyring { }; } secondrequest().then(function(answer) { - for (let i=0; i < answer.keys.length; i++){ + for (let i=0; i < result.keys.length; i++){ if (prepare_sync === true){ - result.keys[i].hasSecret = undefined; if (answer && answer.keys) { for (let j=0; j < answer.keys.length; j++ ){ |