Fix jsDoc to allow @exception tag on ECMAScript 5 properties...

[mramato]

Documenting an exception on an ES5 property changes the property type to the exception type. In the below example, aValue shows up in the generated doc as type DeveloperError, instead of type Element. Removing the exception doc makes the problem go away.

/**
 * Gets or sets a value
 * @memberof MyClass.prototype
 * @type {Element}
 * @exception {DeveloperError} an error!
 */
aValue : {
    get : function() {
        return this._value;
    },
    set : function(value) {
        if (typeof value === 'undefined') {
            throw new DeveloperError('an error!');
        }
        this._value = value;
    }
}

[mramato]

CC @shunter @kristiancalhoun @emackey

[pjcozzi]

@shunter is this fixed after the JSDoc upgrade?

[shunter]

No.

[pjcozzi]

@shunter should this be listed as a JSDoc-specific problem in #1684?

[pjcozzi]

@shunter should this be listed as a JSDoc-specific problem in #1684?

?

[shunter]

I think so. I don't think we can fix it externally.

[pjcozzi]

Does anyone know if this is still an issue?

[pjcozzi]

Upgrading to the latest JSDoc should fix this, #1859 (comment)

For a test case, check http://cesiumjs.org/releases/1.34/Build/Documentation/Model.html?classFilter=Model#boundingSphere

[andynines]

Can this issue be closed? I can reconfirm @bampakoa's comment on #1859 that the problem is no longer present; I generated a test doc page using JSDoc 3.6.11 (the version my NPM resolved to from the version requirements of the package.json in the main branch) and the configuration found in Tools/jsdoc/conf.json.

[ggetz]

Yes, I can confirm the issue is fixed prior to the minimum version of jsdoc in package.json.

Thanks @andynines!