Currently @Arguments supports an arity field which actually acts as a constraint on the maximum arity of the arguments rather than specifying how many values are expected. This is confusing because it differs from what the arity field on @Option does.
Since we now have the restrictions system and specifically the @MaxOccurrences annotation it would be better to deprecate this field and encourage use of the appropriate restriction annotation instead.
Therefore it is proposed to deprecate it in 2.1.x and then remove it in 2.2.x
Currently
@Arguments
supports anarity
field which actually acts as a constraint on the maximum arity of the arguments rather than specifying how many values are expected. This is confusing because it differs from what thearity
field on@Option
does.Since we now have the restrictions system and specifically the
@MaxOccurrences
annotation it would be better to deprecate this field and encourage use of the appropriate restriction annotation instead.Therefore it is proposed to deprecate it in 2.1.x and then remove it in 2.2.x