# Adding user attributes to the directory item serializer

**URL:** <https://meta.discourse.org/t/adding-user-attributes-to-the-directory-item-serializer/130927>\
**Category:** Development\
**Created:** [October 14, 2019, 6:45am UTC](https://meta.discourse.org/t/adding-user-attributes-to-the-directory-item-serializer/130927 "2019-10-14T06:45:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [October 17, 2019, 6:10am UTC](https://meta.discourse.org/t/adding-user-attributes-to-the-directory-item-serializer/130927/3 "2019-10-17T06:10:48Z")

</div>

> [@angus](#):
>
> However, after discussing it further, I determined that one approach could be to make a PR into core which adds user attributes to the directory item serializer via a site setting.

I think @blake and @awesomerobot is working with another customer with similar requirements. I am kind of open for a site setting like we have `always_include_topic_excerpts`

Caveat is that I would like this tested and I would like the site setting to be hidden.

I know @david has been interested in the problem as well, I am a bit mixed here but maybe a longer term solution here that is cleaner is:

1. Add hidden site settings for “allow plugins and themes to opt for extra serialized info” default off
2. Then have a protocol in themes/plugins for “asking” for the extra info.

The advantage here is that some themes then will have the extra serialized info and some not.

I would like to wait on David a bit here before giving you a green light.

---

_[View the full topic](https://meta.discourse.org/t/adding-user-attributes-to-the-directory-item-serializer/130927)._
