# Errors in Liveview: Parse error ... expected attribute name

**URL:** <https://forum.elixirforum.com/t/errors-in-liveview-parse-error-expected-attribute-name/55423>\
**Category:** Questions\
**Tags:** phoenix, liveview, liveview-form, changeset\
**Created:** [April 21, 2023, 2:11am UTC](https://forum.elixirforum.com/t/errors-in-liveview-parse-error-expected-attribute-name/55423 "2023-04-21T02:11:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![boiserunner](https://forum.elixirforum.com/letter_avatar_proxy/v4/letter/b/7bcc69/32.png) [@boiserunner](https://forum.elixirforum.com/u/boiserunner)\
**Post date:** [April 21, 2023, 3:52am UTC](https://forum.elixirforum.com/t/errors-in-liveview-parse-error-expected-attribute-name/55423/2 "2023-04-21T03:52:49Z")

</div>

An update in case it’s helpful. I can certainly pattern match like:

```elixir
<.error :for={{:email, {error_msg, _}} <- @changeset.errors}>
  <%= error_msg %>
</.error>

```

However, I suspect I’m still doing something wrong. The docs for `phx-feedback-for` seem to indicate that wrapping my error with a field value like `:email` would filter errors just for that field. But I have to explicitly match on `:email` to avoid multiple error messages appearing in one spot. It just feels a bit cumbersome or redundant, but it works.

---

_[View the full topic](https://forum.elixirforum.com/t/errors-in-liveview-parse-error-expected-attribute-name/55423)._