Fix merge conflict in reference manual
This commit is contained in:
parent
f2506ca7a1
commit
4d7b265258
|
@ -1749,14 +1749,10 @@ controller. The following code snippet shows the usage:
|
||||||
|
|
||||||
[TIP]
|
[TIP]
|
||||||
====
|
====
|
||||||
<<<<<<< HEAD
|
|
||||||
Unlike the Servlet API "request parameter" concept that conflates query parameters, form
|
Unlike the Servlet API "request parameter" concept that conflates query parameters, form
|
||||||
=======
|
|
||||||
Unlike the Servlet API "request paramater" concept that conflate query parameters, form
|
|
||||||
>>>>>>> parent of 7e91733502... Infer HTTP 404 from empty Optional/Publisher types
|
|
||||||
data, and multiparts into one, in WebFlux each is accessed individually through the
|
data, and multiparts into one, in WebFlux each is accessed individually through the
|
||||||
`ServerWebExchange`. While `@RequestParam` binds to query parameters only, you can
|
`ServerWebExchange`. While `@RequestParam` binds to query parameters only, you can use
|
||||||
use data binding to apply query paramerters, form data, and multiparts to a
|
data binding to apply query parameters, form data, and multiparts to a
|
||||||
<<webflux-ann-modelattrib-method-args,command object>>.
|
<<webflux-ann-modelattrib-method-args,command object>>.
|
||||||
====
|
====
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue