Skip to content

docs(input): update docs to describe md-input-container rather than md-input #2256

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

Merged
merged 3 commits into from
Dec 16, 2016

Conversation

mmalerba
Copy link
Contributor

No description provided.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 16, 2016
@jelbourn
Copy link
Member

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Dec 16, 2016
@jelbourn jelbourn merged commit 20ee360 into angular:master Dec 16, 2016
@arlowhite
Copy link

Thanks for the hard work on angular/material2

Just wanted to mention that it's confusing when the GitHub documentation does not match the latest release in npm. Maybe change the md-input link in the root README.md to the last release branch? But this might be a mess to maintain and confuse/frustrate developers working on master.

What if you set the default GitHub branch to the last release? That way users browsing GitHub as their documentation source are looking at a snapshot of the documentation matching the latest released package.

Or just when you make API changes, such as this md-input change, put a version note in the new API section(s) on that Component's page:

Requires @angular/material2 2.0.0-alpha.12 or greater

@mmalerba mmalerba deleted the input-readme branch December 25, 2016 23:37
@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker 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.

4 participants