Improve consistency in API of FormFields maxFields and maxLength #12718
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't like the usage of
-1
for a defaultmaxFields
andmaxLength
value as we already have methods which don't take thesemaxFields
andmaxLength
parameters which will give you a default value anyway.But if we decide to use
-1
for a default value we should make it consistent across the other non-deprecated methods.Methods like
CompletableFuture<Fields> from(Request request, Charset charset, int maxFields, int maxLength)
are still using -1 for unlimited, but these are deprecated.