Skip to content

Fix empty view rendering #1557

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

Closed
wants to merge 3 commits into from
Closed

Fix empty view rendering #1557

wants to merge 3 commits into from

Conversation

JonRowe
Copy link
Member

@JonRowe JonRowe commented Feb 23, 2016

This fixes two regressions that were introduced by #1535.

Closes #1556
Closes #1551

/cc @samphippen @pixeltrix

super
end
end

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't this just end up adding an uninitialised EmptyTemplateResolver to the view paths array?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes but that's the point, the parts of this that are used are here and don't depend on initialisation.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This bit is to fix #1551 isn't it? If so adding your custom resolver instance to the view path with result in an instance of EmptyTemplateResolver with a nil path instance variable instead. I thought the idea would be to put the custom resolver into the path without wrapping it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't want a custom resolver in the path, the aim is to disable view rendering, my understanding is that would do the opposite.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but it'd generate template missing errors because find_templates would be called on the EmptyTemplateResolver instance and not the custom resolver instance.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well we need to find a way to pass the details of the resolver down into that implementation without loosing this subclass, alternatively we could monkey patch the instance of the resolver with the required methods but I'd rather not do that, that seems dangerous

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is that when path is a Resolver instance, it knows how to look up templates. And the super call in this EmptyTemplateResolver#find_templates doesn’t call up to that resolver.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see #1568 #1580 for a changed implementation that works for my spec suite.

Update: #1568 has been superseded by #1580.

@JonRowe
Copy link
Member Author

JonRowe commented Mar 28, 2016

Closed in prerferance to #1580

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

append_view_path monkey patch breaks API
3 participants