I've done the same in#18134 to easily normalize prototype options, but haven't pushed it yet (there is more to come).

#18134 is just a proof of concept for now, so I guess it's good to have this one as a stand-alone too ;)

whats the problem of callingsetNormalizer multiple times? callingsetNormalizer('a', $f) makes it perfectly clear that$f normalizes all values of optiona, but callingsetNormalizer([ 'a', 'b' ], $f) isnt as clear: does$f operate on each single optiona andb or does it normalize the combination of both[ 'a', 'b' ]?

@backbone87 actuallysetDefined andsetRequired works that way.

@HeahDude These methods have no additional arguments, so its less confusing. But the whole interface shifted more towards a "one call per option" in the recent versions, but the "array set" possibilities didnt got removed (BC). I dont think its a good idea to soften or reverse this path now.

@backbone87 I agree. however for handling prototypes like in#18134 it can make sense, my version to come is a new methodsetNormalizerForAll

@backbone87 nothing wrong with callingsetNormalizer multiple times, this is just syntactic sugar 😄.

i didn't know the whole interface shifted to "one call per option".

closing this PR in favor of interface reliability.

i didn't know the whole interface shifted to "one call per option".

at least that is my interpretation of recent changes, you dont need to close this PR and wait for feedback from some symfony members or@webmozart in this particular case

I agree with the decision to close this ticket. I don't think this kind of syntactic sugar is needed. :)