Layout not being used when "/src/layouts" doesn't exist and layout provides by plugin.

[pauldotknopf]

I am wrapping my theme/styles/pages/etc in a gatsby plugin.

Inside of my plugin, I create the default ``index``` layout.

export const createLayouts = ({ graphql, boundActionCreators }) => {
    const { createLayout } = boundActionCreators;
    const defaultLayout = slash(path.resolve(path.join(__dirname, 'layouts/index.js')));
    createLayout({
        component: defaultLayout,
        id: 'index',
    })
};

My custom plugin is used, but only if a file matches /src/layouts/index.* exists, like /src/layouts/index.sdfwefw.

I think it may have something to do with this line:

gatsby/packages/gatsby/src/redux/actions.js

Line 244 in 6ac0eb9

joinPath(store.getState().program.directory, `src/layouts/index.*`)

My requirements require me to have a directory with pure markdown files. I'm building a tool that is geared more towards non-developers. I'd like to avoid having this magical /src/layouts/index.sdfsf existing.

[pauldotknopf]

Temporary workaround:

export const onCreatePage = ({ page, boundActionCreators }) => {
    const { createPage, deletePage } = boundActionCreators;
    let newPage = page || {};
    if (!newPage.layout) {
        newPage.layout = 'index';
        deletePage(newPage);
        createPage(newPage);
    }
};

[KyleAMathews]

Yeah, we special case src/layouts/index.js as it's so common. What you did in the previous comment is what's required for custom layouts.

[pauldotknopf]

Maybe you should log if a page doesn't have a layout? Why not always set "index" as the default, and let the cli barf when it tries to use the non-existent layout?

Either way, it isn't good to have imperative magic that depends on something seemingly so unrelated. At least at some logging around it, it would have save me a lot of time.

[KyleAMathews]

Yeah, we're actually removing layouts for v2 as they're kinda problematic for a lot of reasons #3830