Skip to content
This repository was archived by the owner on Aug 26, 2024. It is now read-only.
This repository was archived by the owner on Aug 26, 2024. It is now read-only.

Clarity on fallback behavior #35

@eprothro

Description

@eprothro

Gents, I've used mobylette on a few projects over the years and have had a few fallback issues at times -- I think I assumed they were all fixed in 3.x, but ran into a few again. So, first I wanted to start this discussion to see what the expected fallback behavior is.

Gherkin just for clarity...

Given the request for "pages#primary" is a mobile request
And "views/pages/primary.html.haml" exists
And "views/pages/primary.mobile.haml" does NOT exist
And the primary view template renders the "partial" partial
And "views/pages/_partial.html.haml" exists
And "views/pages/_partial.mobile.haml" exists
When the partial is rendered

I would expect the fallback behavior to result in:

Then the "_partial.mobile.haml" file is rendered

However my experience is:
I would expect the fallback behavior to be:

Then the "_partial.html.haml" file is rendered

There are similar behaviors with layout rendering.

What is the desired behavior form your perspective?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions