template-only-glimmer-components: Add support for pods and mixed layouts

[Turbo87]

Resolves one part of #7

/cc @chancancode @rwjblue

[rwjblue]

There is a decent amount of duplication here between the "pods without prefix" and "pods with prefix", can we remove it? Also, the implementation doesn't currently support all pods formats (e.g. app/some-component-name/template.hbs).

At first, I thought that removing the two branches in favor of something like this would solve both scenarios, avoid duplication, and support the missing pods scenario (app/some-component-name/template.hbs), but this has the issue of adding component.js files for route templates which is annoying.

    componentsRoot = path.join(root, `app/${podsFolder}/components`);
    templateCandidates = yield p(glob)('**/template.hbs', { cwd: 'app' });

    templateCandidates.forEach(template => {
      let templatePath = path.join('app', template);

      let jsPath = path.join('app', template.replace(/template\.hbs$/, 'component.js'));
      if (fs.existsSync(path.join(root, jsPath))) return;

      let tsPath = path.join('app', template.replace(/template\.hbs$/, 'component.ts'));
      if (fs.existsSync(path.join(root, tsPath))) return;

      templates.push(templatePath);
      components.push(jsPath); // Always offer to create JS
    });

🤔

[Turbo87]

There is a decent amount of duplication here between the "pods without prefix" and "pods with prefix", can we remove it?

we could, but I'm not sure the code will be that much easier to read afterwards. since it's only used twice I felt that it wasn't worth extracting a function for it

doesn't currently support all pods formats (e.g. app/some-component-name/template.hbs).

I am not aware of that format. I was under the impression that for pods the templates always have to be in the components folder.

Even without support for this particular format this seems like an incremental improvement and we can add support for that other format later?

[rwjblue]

Yep, agreed!