SimpleChat does not work with data model properly.

It happens often for TextField in simple-chat-like renderers.

May be it makes sense to add validation to our evals to check for leading '/' in text field value.

---

### 2 comment(s) from the original issue

**[polina-c](https://github.com/polina-c)** commented on 2026-05-11:

@gspencergoog , @jiahaog

What do you think about adding validation to evals to catch this issue?

Or it will be better to add e2e test to simple chat to try to catch this?

---

**[jiahaog](https://github.com/jiahaog)** commented on 2026-05-11:

It sounds like the a2ui json is not generated by the model correctly? Agreed on evals, we can probably add a set of programatic validations for evals in the A2UI repo.

The issue mentions a problem with TextField in simple-chat-like renderers where a leading '/' may cause issues. Look at the A2UI repository's evals or validation logic, likely in the a2ui repo. Start by finding where simple chat components are defined and how data models are validated. Check for existing e2e tests for simple chat to understand the failure mode. Adding a validation check for leading '/' in text field values in the evals or creating a programmatic validation test is the goal.

Rédigé par le modèle d'indexation à partir du texte de l'issue.