-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document ZPublisher request parameter controls #636
Comments
I like the idea to have the documentation near the code although it should be in the documentation, too to be easily findable. |
Michael Howitz wrote at 2019-5-20 23:15 -0700:
I like the idea to have the documentation near the code although it should be in the documentation, too to be easily findable.
We could first put is near the code (I have seen that this
is already used in `Products.Transience`) and put it in a more
prominent place later - once it is finished and "polished".
Or we put a reference at a prominent place to the location
in the code tree.
|
d-maurer
added a commit
that referenced
this issue
May 24, 2019
d-maurer
added a commit
that referenced
this issue
May 24, 2019
d-maurer
added a commit
that referenced
this issue
Jun 7, 2019
* document request paramter handling #636 * document request paramter handling #636 * apply the improvements proposed by @jirmac00 * - wording and grammar changes * - merging the documentation into the ZDG * - point to the Zope Developer's Guide * - updates following Dieter's suggestions * remove `src/ZPublisher/request_params.rst` as its content is now integrated in `docs/zdgbook/ObjectPublishing.rst` * bring request lookup order documentation in line with reality * remove items from the "converter" list which are now classified as "aggregator" use the same formatting type for "aggregator"s as for "converter"s * Follow suggestion from icemac Co-Authored-By: Michael Howitz <mh@gocept.com> * Follow suggestion from icemac Co-Authored-By: Michael Howitz <mh@gocept.com> * Follow suggestion from icemac Co-Authored-By: Michael Howitz <mh@gocept.com>
Closed via #640 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ZPublisher
(more preciselyZPublisher.HTTPRequest,processInputs
) supports a large set of controls which guide the interpretation of request parameters. A request parameter (as supported by Zope) has the general formname=value
. Controls are specified as suffixes of the form:<control>
to the name part of the request parameter. They can specify for example a type for the value or how the parameter should be aggregated with other request parameters to form a complex form variable. Examples arex:int=1
(gives a form variablex
with integer value1
) andr.x:record=1
(gives a form variabler
with attributex
with value'1'
).The discussions in #618 and #634 have shown that we need a specification/documentation of these features.
Where should such a documentation/specification be located?
request_parameter_controls.rst
alongsideHTTPRequest
with a reference in the docstring of itsprocessInputs
to this filewith alternatives:
processInputs
Such a document would have wide ranging effects:
The text was updated successfully, but these errors were encountered: