Skip to content
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.

Sign up for GitHub

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

Jump to bottom

JSONP renderer currently requires a request object #1535

Closed
mmerickel opened this issue Jan 21, 2015 · 0 comments
Closed

JSONP renderer currently requires a request object #1535

mmerickel opened this issue Jan 21, 2015 · 0 comments
Labels
bugs
Milestone
1.6

Comments

@mmerickel
Copy link
Member

In general the rendering subsystem is expected to work without a request object, which is weird but the way it is.
@mmerickel mmerickel added the bugs label Jan 21, 2015
@mmerickel mmerickel changed the title JSONP renderer currently requires a request object. JSONP renderer currently requires a request object Jan 21, 2015
@mmerickel mmerickel added the 1.6 label Jan 21, 2015
@mmerickel mmerickel mentioned this issue Jan 21, 2015
Closed
mmerickel added a commit that referenced this issue Feb 6, 2015
@mmerickel
Merge pull request #1561 from Pylons/fix.jsonp-without-request
4b13e0d 
fix #1535 by avoiding the request if it's None
mmerickel added a commit that referenced this issue Feb 6, 2015
@mmerickel
backport #1535 by avoiding the request if it's None
9616e20
mmerickel added a commit that referenced this issue Feb 6, 2015
@mmerickel
Merge pull request #1562 from Pylons/backport-fix.jsonp-without-request
7a43ed8 
backport #1535 by avoiding the request if it's None
@mmerickel mmerickel modified the milestone: 1.6 Feb 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugs
Projects
None yet
Milestone
1.6
Development

No branches or pull requests
1 participant
@mmerickel