# Core-2.19 templating changes - preview and testing

**URL:** <https://forum.ansible.com/t/core-2-19-templating-changes-preview-and-testing/40759>\
**Category:** Project Discussions\
**Tags:** fedora, aap, templating, awx, ansible-lint, ansible-core\
**Created:** [March 3, 2025, 9:43pm UTC](https://forum.ansible.com/t/core-2-19-templating-changes-preview-and-testing/40759 "2025-03-03T21:43:27Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![bcoca](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bcoca/32/9269_2.png) [@bcoca](https://forum.ansible.com/u/bcoca)\
**Post date:** [April 16, 2025, 4:28pm UTC](https://forum.ansible.com/t/core-2-19-templating-changes-preview-and-testing/40759/20 "2025-04-16T16:28:40Z")

</div>

Data tagging is mostly revamp of the templating system.

For playbook authors the main features would be:

- Better error information, details should be much clearer and precise
- Stronger data types, templating now does a much better job preserving the data types, less numbers converted to strings.
- Conditionals are now more strictly evaluated, previouslly some things passed as true/false when they should have been templating errors.
- More secure templating, Ansible switched from ‘trusted by default’ to ‘untrusted by default’, this also allows us to remove a lot of processing/filtering/tagging we did to prevent vulnerabilities.

For developers, they get a lot of the above, but DT also signals the start of a new way of writing the internal APIs, clearly signaling what is internal (`_internal` prefixed/subdir) and documenting and making explicit which APIs are available for which plugins.

---

_[View the full topic](https://forum.ansible.com/t/core-2-19-templating-changes-preview-and-testing/40759)._