deprecate ExactValidArgs in favour of MatchAll(OnlyValidArgs, ...)#1646
deprecate ExactValidArgs in favour of MatchAll(OnlyValidArgs, ...)#1646umarcor wants to merge 1 commit into
Conversation
|
Any reason for splitting this up into multiple PRs? Generally, I think i'd prefer to tackle in as few PRs as possible. But if it makes sense to do multiple, that's fine. I don't have a ton of context on this, so let me familiarize myself and get back on this |
Having it all together did delay the contribution several years, because it was apparently too much to tackle. Splitting into smaller pieces is allowing to slowly get the content merged. On the other hand, according to ab42c93, #1643 might produce an error because it modifies more than 200 lines.
See #1643 (comment). |
fbc89dd to
bf863a9
Compare
bf863a9 to
d657f87
Compare
|
@jpmcb can we please merge this M-sized PR, to move forward with the series? |
50536cd to
ba01e0f
Compare
3138153 to
843f4f2
Compare
|
@jpmcb @marckhouzam @johnSchnake can we please address this before the spring is over? |
|
I vote for merging #1643 directly |
|
#1643 is a superset, so merging any of them will solve this. |
843f4f2 to
3e01214
Compare
676dab9 to
6d429ac
Compare
6d429ac to
7985055
Compare
7985055 to
cbd7c48
Compare
This is a subset of #1643, which is a subset of #841.