Skip to content

Conversation

@nathanmarks
Copy link
Contributor

Adds the value as the 2nd callback argument for onChange and removes valueLink as per #2957 and #2880

  • PR has tests / docs demo, and is linted.
  • Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
  • Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

@nathanmarks
Copy link
Contributor Author

Force pushed a ninja change to my test... 😜

@nathanmarks nathanmarks added this to the 0.15.0 Release milestone Mar 16, 2016
@nathanmarks
Copy link
Contributor Author

FYI, I'm tending to EnhancedTextarea in another PR 👍

@oliviertassinari
Copy link
Member

That looks good to me 👍.

@alitaheri
Copy link
Collaborator

Ok I'll merge this. Hopefully people won't complain 😆 😆

alitaheri added a commit that referenced this pull request Mar 17, 2016
[TextField] Standardize onChange callback and remove valueLink
@alitaheri alitaheri merged commit 03f1f0b into mui:master Mar 17, 2016
@zannager zannager added the scope: text field Changes related to the text field. label Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

scope: text field Changes related to the text field.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants