Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The [Required] attribute is not respected
See original GitHub issueThe [Required] (RequiredAttribute) decorator has no effect.
public class Model
{
[Required]
public string Name { get; set; }
}
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:14 (4 by maintainers)
Top Results From Across the Web
html - form field required not working
Try using the placeholder attribute to display your 'label' inside of the <input /> and remove the value attribute. This way, required is ......
Read more >LWC: lightning-record-form not respecting required ...
I have the following LWC Component: " " I have created a Page Layout for the recordType and marked a few fields as...
Read more >HTML Required Not Working: 5 Issues That Cause It
The name is not a required element but a mandatory attribute identifier. Fields with no names are not considered part of the submission...
Read more >HTML attribute: required - MDN Web Docs
The Boolean required attribute, if present, indicates that the user must specify a value for the input before the owning form can be ......
Read more >RequiredAttribute Class (System.ComponentModel. ...
The RequiredAttribute attribute specifies that when a field on a form is validated, the field must contain a value. A validation exception is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same problem on v1.1.0 AspNetCore
I’m also getting this issue on v1.1.0