# ember/template-no-args-paths 💼 This rule is enabled in the 📋 `template-lint-migration` [config](https://github.com/ember-cli/eslint-plugin-ember#-configurations). 🔧 This rule is automatically fixable by the [`--fix` CLI option](https://eslint.org/docs/latest/user-guide/command-line-interface#--fix). Arguments that are passed to components are prefixed with the `@` symbol in Angle bracket syntax. Ember Octane leverages this in the component's templates by allowing users to directly refer to an argument using the same prefix: ```gjs ``` We can immediately tell now by looking at this template that `@todos` is an argument that was passed to the component externally. This is in fact _always true_ - there is no way to modify the value referenced by `@todos` from the component class, it is the original, unmodified value. ## Examples This rule **forbids** the following: ```gjs ``` ```gjs ``` ```gjs ``` This rule **allows** the following: ```gjs ``` ```gjs ``` ## Migration - find in templates `this.args.` replace to `@` ## Related Rules - [no-curly-component-invocation](no-curly-component-invocation.md) ## References - [RFC #276](https://github.com/emberjs/rfcs/blob/master/text/0276-named-args.md) - [Coming Soon in Ember Octane - Part 2: Named Argument Syntax](https://www.pzuraq.com/blog/coming-soon-in-ember-octane-part-2-angle-brackets-and-named-arguments/#namedargumentsyntax) - [Named arguments in Ember.js](https://www.balinterdi.com/blog/named-arguments-in-ember-js/) - [ember-named-arguments-polyfill](https://github.com/rwjblue/ember-named-arguments-polyfill)