-
Notifications
You must be signed in to change notification settings - Fork 886
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
add InstancePropertyHelper and apply_request_extensions #1581
Conversation
LGTM |
That little edit to IRequestFactory was because IRequestFactory is a public api and IRequest is apparently not. So I didn't want the private api referenced from the public docstring. |
I had not realised that |
Well I actually thought it was. But it's private and just a marker interface actually. |
add InstancePropertyHelper and apply_request_extensions
|
||
After invoking this method, the ``request`` should have the methods | ||
and properties that were defined using | ||
:meth:`pyramid.config.Configurator.add_request_method`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we document how you would use extensions
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I explicitly left extensions
off of the public api documentation. It's there just for pyramid's hot route in the router. The IRequestExtensions
interface is private and shouldn't be used/passed-in directly by anyone. We do this in a few other places in the code for testing hooks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could name it _extensions
if it would make you feel better.
No description provided.