# Writing future proof components for Ember 2.0

**URL:** <https://discuss.emberjs.com/t/writing-future-proof-components-for-ember-2-0/8294>\
**Category:** Design\
**Created:** [June 30, 2015, 4:19pm UTC](https://discuss.emberjs.com/t/writing-future-proof-components-for-ember-2-0/8294 "2015-06-30T16:19:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![amk](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/amk/32/9116_2.png) [@amk](https://discuss.emberjs.com/u/amk)\
**Post date:** [June 30, 2015, 4:19pm UTC](https://discuss.emberjs.com/t/writing-future-proof-components-for-ember-2-0/8294/1 "2015-06-30T16:19:17Z")

</div>

It’s a bit tricky to write and test Ember code during this in-between phase of having some (but not all) of Ember 2.0’s new patterns.

I’m specifically struggling with trying to mimic the forthcoming one-way behaviour of 2.0 in 1.13.2

Consider `<my-component foo=foo />`, where `foo` will be immutable

But:

```
{{my-component foo=foo}}

didInitAttrs() {
  this.set('foo', this.getAttr('foo'));
}

```

…foo is still mutable.

See this [simple fiddle](http://jsfiddle.net/amk221/8ctscr9a/).

Is there an `immutable` helper for aid in the transition to Ember 2.0?