> 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/0151-to-0179/aur0177.md).

# AUR0177

## Error Message

`AUR0177: Expression error: object binding patterns only support identifiers and aliases with unique, non-reserved local names: "{{expression}}"`

## Description

Object destructuring in a `repeat.for` declaration supports shallow property names and aliases whose targets are unique local identifiers. Aurelia reports this error when a parsed object declaration uses a nested pattern, an expression target, the same local name more than once, a repeat contextual name such as `$index`, the reserved `$item` name, or an Object prototype name such as `constructor`. Source properties with reserved names remain available through a safe alias.

## Example Trigger

```html
<!-- ❌ Nested object patterns are not supported -->
<div repeat.for="{ customer: { name } } of orders">
  ${name}
</div>
```

## Solution

Use shallow locals or repeat the complete object when the template needs more complex access:

```html
<!-- ✅ Shallow property and alias -->
<div repeat.for="{ id: orderId, customer } of orders">
  ${orderId}: ${customer.name}
</div>

<!-- ✅ A reserved source property can use a safe local alias -->
<div repeat.for="{ constructor: type } of orders">
  ${type}
</div>

<!-- ✅ Keep the complete object -->
<div repeat.for="order of orders">
  ${order.id}: ${order.customer.name}
</div>
```


---

# 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/0151-to-0179/aur0177.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.