# Possible to use custom file structure & file naming?

**URL:** <https://discuss.emberjs.com/t/possible-to-use-custom-file-structure-file-naming/13884>\
**Category:** Uncategorized\
**Created:** [November 16, 2017, 1:31pm UTC](https://discuss.emberjs.com/t/possible-to-use-custom-file-structure-file-naming/13884 "2017-11-16T13:31:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nima](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/nima/32/17616_2.png) [@nima](https://discuss.emberjs.com/u/nima)\
**Post date:** [November 16, 2017, 1:31pm UTC](https://discuss.emberjs.com/t/possible-to-use-custom-file-structure-file-naming/13884/1 "2017-11-16T13:31:36Z")

</div>

I want to use the following file structure _ **and** _ file naming:

```
/app
  /components
    /some-component
      component.some-component.template.hbs
      component.some-component.class.js
  /routes
    /some-route
      route.some-route.handler.js
      route.some-route.template.hbs
      route.some-route.controller.js
  /models
   model.some-model.js

```

It’s _kind of_ similar to the `pods` structure but it’s not exactly it since the file naming is totally different.

Any hints on how I can achieve this? I tried overriding Resolver methods as it’s been suggested [here](https://discuss.emberjs.com/t/serving-all-routes-from-a-specific-folder-using-pods/8581/9) but this is only for when you use `pods` and you simply want to group all of you route-folders in one parent-folder.

---

<div class="post-metadata">

**Author:** ![rwjblue](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/rwjblue/32/9411_2.png) [@rwjblue](https://discuss.emberjs.com/u/rwjblue)\
**Post date:** [November 27, 2017, 1:54pm UTC](https://discuss.emberjs.com/t/possible-to-use-custom-file-structure-file-naming/13884/2 "2017-11-27T13:54:05Z")

</div>

It is absolutely a design constraint of the system that you _can_ do this by overriding the correct methods in the resolver, but I would **strongly** suggest against it. You will have significant pain, and loose out on one of the largest selling point of Ember: community shared solutions…