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.
Refactor Field validation
See original GitHub issueProblem statement
Currently, field.validator_ is called in some of the methods of classes that inherit from Field, but not called in the Field class itself (whether by callValidator(..) or more direct methods). When and where the validators are called in the field classes is not standardized and therefore makes coding and fixing bugs for all field types difficult. It would therefore be more consistent to have the callValidator(..) method called in the Field setValue method.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think @BeksOmega’s suggestion will work, and it looks like it’ll work for backwards compatibility. This is another case where we should have tests that are the same before and after, to verify that existing implementations continue to work.
Closing as the original issue is fixed, and I think the secondary events issue was a misdiagnosis of the problem.