# Overriding VM class name convention

**URL:** <https://discourse.aurelia.io/t/overriding-vm-class-name-convention/3180>\
**Category:** Framework Knowledge\
**Created:** [January 22, 2020, 4:33pm UTC](https://discourse.aurelia.io/t/overriding-vm-class-name-convention/3180 "2020-01-22T16:33:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![RomkeVdMeulen](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/romkevdmeulen/32/28_2.png) [@RomkeVdMeulen](https://discourse.aurelia.io/u/RomkeVdMeulen)\
**Post date:** [January 22, 2020, 4:33pm UTC](https://discourse.aurelia.io/t/overriding-vm-class-name-convention/3180/1 "2020-01-22T16:33:22Z")

</div>

I needed to override the naming convention for VM class names: I wanted to be able to name VM’s attached to routes something like `EmailRoute` which might contain a `EmailComponent`.

I didn’t find a built-in configuration to do this, but it turned out to be pretty easy to make an override. I wrote a short [blog post](https://romkevandermeulen.nl/2020/01/22/aurelia-vm-class-naming-convention.html) about it.

I thought I’d mention it here in case anyone with similar needs does a search.