-
Notifications
You must be signed in to change notification settings - Fork 486
Add support for documenting class properties #417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can these be documented using |
That did work, thanks for the heads-up! Although, it'd be great if I didn't have to use those 2 extra tags. export default class ModelBase {
/**
* Plugins to be used for the current ORM instance.
* @type {Object[]}
* @memberof ModelBase
* @static
*/
static plugins = [];
} For those who are curious, my actual implementation mentioned above can be found here. |
If you leave out |
No, the context is not detected correctly: in the example above, |
🍏 This works in current documentation.js 5.x In:
Out:
|
https://github.com/jeffmo/es-class-fields-and-static-properties
Adding support for documenting those would greatly improve my workflow, as I would't have to explicitly use getters and setters for each class property. Also, the
@property
JSDoc tag before aclass
declaration doesn't behave as expected for my use case.The text was updated successfully, but these errors were encountered: