# Role var/param naming (prefix)

**URL:** <https://forum.ansible.com/t/role-var-param-naming-prefix/1855>\
**Category:** Get Help\
**Tags:** collections, galaxy-ng\
**Created:** [October 22, 2023, 12:19am UTC](https://forum.ansible.com/t/role-var-param-naming-prefix/1855 "2023-10-22T00:19:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\
**Post date:** [April 6, 2024, 10:14pm UTC](https://forum.ansible.com/t/role-var-param-naming-prefix/1855/2 "2024-04-06T22:14:49Z")

</div>

I’ve [whined about this](http://forum.ansible.com/t/ansible-lint-and-the-role-prefix-on-variable-names-in-collections/2935) but from the other side. That is, I want Fully Qualified Variable Names (FQVN), not just prefixed with the role name. The fact that I have three distinct roles with the same name - one stand-alone and two in collections - makes a role-only prefix not particularly helpful. (It wasn’t my idea! I just implemented 'em, honest!)

`ansible-lint` will complain if you pass un-prefixed variables in a `vars` section of an `include_role` task. But it can’t really complain about a role using variables that aren’t prefixed; it has no way of knowing if those variables are unique to the role or if they come from elsewhere (I’m guessing).

---

_[View the full topic](https://forum.ansible.com/t/role-var-param-naming-prefix/1855)._