modeling: empty lists are not allowed
Do not allow empty lists in configuration.
Merge request reports
Activity
added 1 commit
- b8979ae5 - fixup! datamodel: types: ListOrItem: empty list not allowed
marked this merge request as draft from b8979ae5
added 1 commit
- 876aed22 - datamodel: types: ListOrItem: empty list not allowed
requested review from @vcunat
added 1 commit
- 1273f899 - fixup! datamodel: types: ListOrItem: empty list not allowed
marked this merge request as draft from 1273f899
- Resolved by Vladimír Čunát
I passed through the model and haven't noticed any place where this would cause issues, so I think we could just merge – and later fix any edge cases if they appear.
Nit: in many places it would feel more natural (to me) to have empty list as default, instead of the current wrapping with
Optional
and default ofNone
. But perhaps it's not good costs vs. benefits ratio to change that approach at this point.
mentioned in issue #809
added 7 commits
-
1273f899...6e3d72be - 5 commits from branch
6.0
- 60baef24 - modeling/base_schema.py: empty lists not allowed
- 468c827a - datamodel: types: ListOrItem: empty list not allowed
-
1273f899...6e3d72be - 5 commits from branch
mentioned in commit be05fad9