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

@ -30,8 +30,8 @@ let ChromeCom = {
* 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. When the request cannot be handled, the callback
* is immediately invoked with no arguments.
@ -56,7 +56,7 @@ let ChromeCom = {
/**
* Resolves a PDF file path and attempts to detects length.
*
* @param {String} file - Absolute URL of PDF file.
* @param {string} file - Absolute URL of PDF file.
* @param {OverlayManager} overlayManager - Manager for the viewer overlays.
* @param {Function} callback - A callback with resolved URL and file length.
*/