# Problem tracking nested structure

**URL:** https://meta.discourse.org/t/problem-tracking-nested-structure/320886
**Category:** Development
**Created:** [August 9, 2024, 12:12pm UTC](https://meta.discourse.org/t/problem-tracking-nested-structure/320886 "2024-08-09T12:12:57Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [August 9, 2024, 12:54pm UTC](https://meta.discourse.org/t/problem-tracking-nested-structure/320886/4 "2024-08-09T12:54:30Z")

</div>

This is an unfortunate part of us being midway-through converting from Ember’s ‘classic’ reactivity system (get/set/computed) to the ‘octane’ `@tracked` / native-getters.

So as discussed above, the problem with your example is that you’re accessing a non-`@tracked` property from a native getter.

Accessing the full path directly from a template will work, although as you say, it limits the logic available.

Alternatively, using `.get()` will allow Ember’s new autotracking system to work against classic (i.e. non-`@tracked`) properties.

So in this case, it would be

```js
get statusMessage() {
  return this.args.topic.get("my_metadata.status");
}

```

---

_[View the full topic](https://meta.discourse.org/t/problem-tracking-nested-structure/320886)._