Consistently use string for string data types in JSDoc comments

Sometimes we also used `String`, but `string` is the what the JSDoc
documentation recommends.
This commit is contained in:
Tim van der Meij 2019-10-12 15:59:09 +02:00
parent e75991b49e
commit efd331daa1
No known key found for this signature in database
GPG key ID: 8C3FD2925A5F2762
6 changed files with 13 additions and 13 deletions

View file

@ -32,8 +32,8 @@ let FirefoxCom = (function FirefoxComClosure() {
* synchronously respond to.
* NOTE: It is reccomended to use request() instead since one day we may not
* be able to synchronously reply.
* @param {String} action The action to trigger.
* @param {String} data Optional data to send.
* @param {string} action The action to trigger.
* @param {string} data Optional data to send.
* @return {*} The response.
*/
requestSync(action, data) {
@ -52,8 +52,8 @@ let FirefoxCom = (function FirefoxComClosure() {
/**
* Creates an event that the extension is listening for and will
* asynchronously respond by calling the callback.
* @param {String} action The action to trigger.
* @param {String} data Optional data to send.
* @param {string} action The action to trigger.
* @param {string} data Optional data to send.
* @param {Function} callback Optional response callback that will be called
* with one data argument.
*/