-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
docs(material/button-toggle): add missing type on public API #22224
docs(material/button-toggle): add missing type on public API #22224
Conversation
Adds an explicit type to `MatButtonToggleGroup` so that it can show up in the docs. This change is merge safe, because the type is the same as the inferred type that was in place already. Fixes angular#22026.
@@ -83,7 +83,8 @@ export const MAT_BUTTON_TOGGLE_GROUP_VALUE_ACCESSOR: any = { | |||
multi: true | |||
}; | |||
|
|||
let _uniqueIdCounter = 0; | |||
// Counter used to generate unique IDs. | |||
let uniqueIdCounter = 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for clarification, could you fill me in on why we are making this public? Or is there another reason we're removing the underscore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't make it public, I just removed the underscore since the constant isn't being exported so the name doesn't really matter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Adds an explicit type to
MatButtonToggleGroup
so that it can show up in the docs. This change is merge safe, because the type is the same as the inferred type that was in place already.Fixes #22026.