-
Notifications
You must be signed in to change notification settings - Fork 101
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
Types of accessors are not resolved propery #246
Comments
Can you not use the |
Good point, I saw those two properties on the This document then just had both |
Good spot, it is a bit buggy. Let me come up with a fix. |
I have created a PR which should solve this problem... #247 |
@petebacondarwin Thanks! I will try to give it a shot this today/tomorrow. Will keep you updated. |
Due to angular/dgeni-packages#246 the Material docs package used a workaround for accessor types. The issue has been fixed with angular/dgeni-packages#247 and the workaround can be removed now.
Due to angular/dgeni-packages#246 the Material docs package used a workaround for accessor types. The issue has been fixed with angular/dgeni-packages#247 and the workaround can be removed now.
Due to angular/dgeni-packages#246 the Material docs package used a workaround for accessor types. The issue has been fixed with angular/dgeni-packages#247 and the workaround can be removed now.
Hey there,
With the recent changes to more object orientated documents, the types for accessors are no longer resolved properly.
Also those getters and setters are being treated as functions, while they theoretically can be considered as properties of the class.
This means that right now we need to manually determine the types of the accessors in our Dgeni package.
The issue here is, that the
members
of the class may exist twice and the type of the "property" can be defined in two different places. Either in the getter or in the setter as a first parameter.The text was updated successfully, but these errors were encountered: