-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix validation of steps #1176
Fix validation of steps #1176
Conversation
This failed because the number of validation calls generated have changed. Intermediate steps are validated after setting with the following logic. self._save_val(val_step,
validate=(self.val_mapping is None and
self.set_parser is None and
not(step_index == len(steps)-1 or
len(steps) == 1))) I am not sure I see the need for that if we validate them up front too. Perhaps we should get rid of it. Validating before setting seems like the correct thing to do in any case |
Codecov Report
@@ Coverage Diff @@
## master #1176 +/- ##
==========================================
- Coverage 79.67% 79.66% -0.02%
==========================================
Files 47 47
Lines 6661 6662 +1
==========================================
Hits 5307 5307
- Misses 1354 1355 +1 |
Merge: 0d85481 f7469d1 Author: Jens Hedegaard Nielsen <[email protected]> Merge pull request #1176 from jenshnielsen/fix_validation_of_steps
Fixes #1174
Ensure that intermediate steps are validated too. In general we cannot assume that a step is valid just because the endpoint is