# Reuse view/template in inheritance - migrating from v1

**URL:** <https://discourse.aurelia.io/t/reuse-view-template-in-inheritance-migrating-from-v1/5162>\
**Category:** Help Requests\
**Created:** [May 9, 2023, 12:40pm UTC](https://discourse.aurelia.io/t/reuse-view-template-in-inheritance-migrating-from-v1/5162 "2023-05-09T12:40:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![balazsmeszegeto](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/balazsmeszegeto/32/2335_2.png) [@balazsmeszegeto](https://discourse.aurelia.io/u/balazsmeszegeto)\
**Post date:** [May 9, 2023, 12:40pm UTC](https://discourse.aurelia.io/t/reuse-view-template-in-inheritance-migrating-from-v1/5162/1 "2023-05-09T12:40:01Z")

</div>

I’m migrating v1 app and looking for a solution reusing a view/template in inheritance.  
In v1, one could decorate base class with `@useView(path: string)` and it’d be inherited by subclasses (or override if necessary). Or one could define `getViewStrategy(): string` method on the base (and override in subclass). How is it done in v2?

Should I create static field called on base (such as indicated by on this:  
[Cheat Sheet - The Aurelia 2 Docs](https://docs.aurelia.io/developer-guides/cheat-sheet#custom-elements) )?

I’d be also great if inheritance would be a section in the docs like:  
[Templating: HTML Behaviors Introduction | Aurelia](http://aurelia.io/docs/templating/html-behaviors#inheritance-with-html-behaviors)