Skip to content

docs: add types to public methods and getters/setters #9558

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

Closed
wants to merge 1 commit into from
Closed

docs: add types to public methods and getters/setters #9558

wants to merge 1 commit into from

Conversation

rafaelss95
Copy link
Contributor

@rafaelss95 rafaelss95 commented Jan 24, 2018

Basically, this PR adds the missing types/docs for leftovers after #7711.

Fixes #8832.

PS: It'd be great to use something like typedef to ensure types for getters and setters are specified.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 24, 2018
get role(): string|null {
return this.empty ? null : 'listbox';
}
get role(): string | null { return this.empty ? null : 'listbox'; }
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JSdocs for this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"The ARIA role applied to the chip list"

@rafaelss95 rafaelss95 changed the title docs: add types to public methods and getters/setts docs: add types to public methods and getters/setters Jan 24, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rafaelss95 you may want to break this up into smaller PRs; by changing so many files, it will likely require repeated rebasing

get role(): string|null {
return this.empty ? null : 'listbox';
}
get role(): string | null { return this.empty ? null : 'listbox'; }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"The ARIA role applied to the chip list"

@rafaelss95
Copy link
Contributor Author

rafaelss95 commented Jan 24, 2018

@jelbourn Since there are only changes in docs, wouldn't it be better if you could review and merge it ASAP to prevent the repeated rebase? Do you guys have a certain day to review this kind of PR?

Btw, I've rebased.

@jelbourn
Copy link
Member

The problem is that anything that touches code (including the types) has to go through Google's presubmit process, which means it gets batched in with other PRs. Anything that gets merged earlier in the pipeline would have a potential conflict.

@rafaelss95
Copy link
Contributor Author

rafaelss95 commented Jan 25, 2018

Got it. How do you suggest to break it? What's the criteria?

@jelbourn
Copy link
Member

Up to you, maybe aim for something like 20 files per PR?

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing docs for properties/methods
3 participants