> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/developer-guides/error-messages/0203-to-0227/aur0227.md).

# AUR0227

## Error Message

`AUR0227: Side-effect detected in computed getter '{{getter}}': mutation during evaluation caused self-dirtying. This can lead to infinite recursion. Use non-mutating operations (e.g., spread syntax) or move side effects outside the getter.`

Where `{{getter}}` is the computed getter name (for example `get total`).

## Description

This error occurs when a computed getter (a getter tracked by Aurelia’s observation system) mutates state while it is being evaluated. Mutations during evaluation can “self-dirty” the computed observer and cause repeated re-evaluation (potentially an infinite loop).

## Example Trigger

```ts
export class MyVm {
  items = ['b', 'a'];

  // ❌ Mutates state during evaluation (Array.prototype.sort is in-place)
  get sortedItems() {
    return this.items.sort();
  }
}
```

## Correct Usage

Make computed getters pure (no side effects / no mutation). Use non-mutating operations or compute elsewhere.

```ts
export class MyVm {
  items = ['b', 'a'];

  // ✅ Non-mutating
  get sortedItems() {
    return [...this.items].sort();
  }
}
```

## Troubleshooting

* Identify the computed getter from `{{getter}}` in the message.
* Look for in-place mutations inside the getter (for example `sort`, `reverse`, `push`, `splice`, `++`, assignments).
* Move side effects to explicit actions (methods/event handlers) or effects/watchers, and keep the getter as a pure derivation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aurelia.io/developer-guides/error-messages/0203-to-0227/aur0227.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.