Having two template names, one plural one singular, ignores plural

[Alonski]

I have two different routes:

1. Template
2. Templates

This also generated two templates:

1. template.hbs
2. templates.hbs

When I go to the templates route. Ember tries to render the template.hbs template.

Trying to use templateName or renderTemplate() doesn't work.
// app/routes/templates.js export default Ember.Route.extend({ templateName: "templates", renderTemplate() { this.render("templates"); } });

Here is a twiddle made by @gmarquet
https://ember-twiddle.com/c3f1c16b8fb0ca56248b767a09acd3c9?openFiles=twiddle.json%2C&route=%2Ftemplates

Got around this currently by renaming the template.hbs to something else and using templateName to set the name for the the template route

[pixelhandler]

@Alonski it may be worth sharing a work around example as well. I see the issue in the ember-twiddle example you provided, this looks like a bug.

[Alonski]

@pixelhandler Hey my workaround was renaming template.hbs to template-single.hbs. Then in the tenplateRoute I have templateName: template-single.hbs.

[locks]

This is likely related to pods.

[Alonski]

@locks To clarify I am not using pods in my App.

[locks]

@Alonski the thing is that the resolver supports both structures at the same time, and as far as I know there's no way to "turn it off", so indirectly you are using pods ;x

What I think is happening here, since you don't have a "pod module prefix" set, it falls back to /app, meaning /app/templates/template.hbs translates to "this is the template file for the templates route". Could you confirm @rwjblue?

The good news is that the module unification structure should not suffer from these kinds of ambiguity.

[pixelhandler]

@Alonski yeah I was suspicious of the name template.hbs glad you had a work around using template-single.hbs. I'll close this for now.

[Alonski]

@pixelhandler I'm not sure this should be closed. Maybe add a workaround in the CLI so you can't create templates named template.hbs