# Unresolved Issue #10098: set()s from jinja are treated as strings

**URL:** <https://forum.ansible.com/t/unresolved-issue-10098-set-s-from-jinja-are-treated-as-strings/21811>\
**Category:** Ansible Developer\
**Created:** [June 19, 2016, 7:53am UTC](https://forum.ansible.com/t/unresolved-issue-10098-set-s-from-jinja-are-treated-as-strings/21811 "2016-06-19T07:53:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hagai\_Kariti](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@Hagai\_Kariti](https://forum.ansible.com/u/Hagai_Kariti)\
**Post date:** [June 19, 2016, 7:53am UTC](https://forum.ansible.com/t/unresolved-issue-10098-set-s-from-jinja-are-treated-as-strings/21811/1 "2016-06-19T07:53:11Z")

</div>

This issue was closed yesterday, but it’s still unresolved. set() type is still treated as a string in Ansible. While an error isn’t thrown when using a set in with\_items, the entire set is treated as a single item, i.e. a string. This behavior isn’t any better than throwing an error. The issue should be re-opened.

Link: [https://github.com/ansible/ansible/issues/10098](https://github.com/ansible/ansible/issues/10098)

Thanks