Skip to content

Conversation

sfnelson
Copy link

Rails rendering assumes that the first prefix encountered is 'special', specifically, it's the controller's prefix. This can be seen in ActionView::AbstractRenderer::ObjectRendering#initialize. This change injects the controller path at the start of the prefix list instead of the end to make sure this assumption is satisfied.

Resolves #2729.

@JonRowe
Copy link
Member

JonRowe commented Apr 10, 2024

👋 Can you rebase this?

Rails rendering assumes that the first prefix encountered is 'special', specifically, it's the controller's prefix. This can be seen in `ActionView::AbstractRenderer::ObjectRendering#initialize`. This change injects the controller path at the start of the prefix list instead of the end to make sure this assumption is satisfied.

Resolves rspec#2729.
@sfnelson sfnelson force-pushed the fix/lookup-context-prefixes branch from 3946746 to 537481e Compare April 10, 2024 12:03
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.

View example group inserts controller path into lookup_context in the wrong order

2 participants