resolve RequestMapping#params

[tangcent]

• resolve org.springframework.web.bind.annotation.RequestMapping#params

---

docs:

The parameters of the mapped request, narrowing the primary mapping.
<p>Same format for any environment: a sequence of "myParam=myValue" style
expressions, with a request only mapped if each such parameter is found
to have the given value. Expressions can be negated by using the "!=" operator,
 as in "myParam!=myValue". "myParam" style expressions are also supported,
with such parameters having to be present in the request (allowed to have
any value). Finally, "!myParam" style expressions indicate that the
specified parameter is <i>not</i> supposed to be present in the request.
<p><b>Supported at the type level as well as at the method level!</b>
When used at the type level, all method-level mappings inherit
this parameter restriction (i.e. the type-level restriction
gets checked before the handler method is even resolved).
<p>Parameter mappings are considered as restrictions that are enforced at
the type level. The primary path mapping (i.e. the specified URI value)
still has to uniquely identify the target handler, with parameter mappings
simply expressing preconditions for invoking the handler.

---

solution:

• !name : append desc "parameter $param should not be present") to the request.
• name : append a new param to the request or set existed param to required.
• name!=value : if param present. append desc "should not equal to [$value]" to the param,otherwise append desc "parameter $param should not equal to [$value]") to the request.
• name=value : append a new param to the request or set existed param to required & valued the given value.