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.
Nested many fields and `pass_original`
See original GitHub issueI took a quick look at the code and I’m not sure it’s a trivial change or if you’d be interested but in my application, I want to verify that no unwanted fields are passed. When I have a nested field with many=True, then I cannot check each one individually for unwanted data being passe. This is because original_data is the list of objects and I’m unsure how I can correctly identify which bit of original_data corresponds to the data.
What are your thoughts?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:5 (3 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
Ohhh,
run_validatoralready has index, so all you’d need to do is an:if index is None then original_data else original_data[index]and that could be an option? or I think a reasonable default? that or pass the index.Thanks!