forms
Here are 1,576 public repositories matching this topic...
-
Updated
Nov 14, 2020 - TypeScript
Are you submitting a bug report or a feature request?
Bug? I guess.
What is the current behavior?
-
Updated
Nov 9, 2020 - Swift
-
Updated
Nov 15, 2020 - Objective-C
-
Updated
Nov 5, 2020 - JavaScript
-
Updated
Oct 31, 2020 - Objective-C
-
Updated
Oct 28, 2020 - TypeScript
-
Updated
Oct 9, 2019 - JavaScript
-
Updated
Nov 14, 2020 - TypeScript
-
Updated
Nov 13, 2020 - JavaScript
-
Updated
Mar 2, 2020 - JavaScript
-
Updated
Sep 15, 2020 - JavaScript
-
Updated
Jun 19, 2020 - JavaScript
-
Updated
Nov 1, 2020 - TypeScript
-
Updated
Nov 6, 2020 - JavaScript
-
Updated
Sep 25, 2019 - Swift
-
Updated
Oct 30, 2020 - TypeScript
-
Updated
Oct 31, 2020 - Python
-
Updated
Nov 13, 2020 - JavaScript
-
Updated
Sep 4, 2020 - TypeScript
-
Updated
Mar 30, 2020 - JavaScript
-
Updated
Nov 5, 2020 - JavaScript
-
Updated
Nov 14, 2020 - JavaScript
Improve this page
Add a description, image, and links to the forms topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the forms topic, visit your repo's landing page and select "manage topics."


Current Behavior
The type
ErrorMessagedoesn't have an id property.Desired Behavior
It'd be nice
id?: stringwould be added to the typeErrorMessageand set on the outermost component that serves as error message.Suggested Solution
Add
id={this.props.id}to the outer component inErrorMessage.Who does this impact? Who is this