# Understanding \`args\` in Glimmer Components

**URL:** <https://discuss.emberjs.com/t/understanding-args-in-glimmer-components/18444>\
**Category:** Blog\
**Created:** [December 23, 2020, 2:13am UTC](https://discuss.emberjs.com/t/understanding-args-in-glimmer-components/18444 "2020-12-23T02:13:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chriskrycho](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/chriskrycho/32/17763_2.png) [@chriskrycho](https://discuss.emberjs.com/u/chriskrycho)\
**Post date:** [December 23, 2020, 2:13am UTC](https://discuss.emberjs.com/t/understanding-args-in-glimmer-components/18444/1 "2020-12-23T02:13:35Z")

</div>

_Clearing up a common confusion with a worked example._ Many developer assume this is more magic going on with Glimmer components’ arguments than there really is. Let’s see how they actually work!

[**Understanding `args` in Glimmer Components**](https://v5.chriskrycho.com/journal/understanding-args-in-glimmer-components/)

> One of the most consistent confusions I see as I support the [LinkedIn.com](http://LinkedIn.com) migration to [Ember Octane](https://emberjs.com/editions/octane/) is how to think about `args` in Glimmer components. In particular, I consistently see people struggling with how to understand _updates_ to `args` what they can and cannot do with them. In this post, I hope to make it much clearer by working through an example of how `args` are passed from component to component, but in plain JavaScript: using a slightly simplified version of the `Component` API with no autotracking in sight. By the end of the post, you should have a clear handle on what will and won’t work in the body of a Glimmer component—and, more importantly, _why_.

[Read the rest!](https://v5.chriskrycho.com/journal/understanding-args-in-glimmer-components/)