FAQ: Directives - Built-in and Custom Directives

This community-built FAQ covers the “Built-in and Custom Directives” exercise from the lesson “Directives”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Learn AngularJS 1.X

FAQs on the exercise Built-in and Custom Directives

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

In this task, the instructions seem to indicate that “ng-repeat” and “ng-click” are both directives, and they goes on to say that, in this instance, <app-info> is also a kind of directive. However, when I look at these things as a front end developer, I would say that two of them look like attributes while <app-info> looks like a brand new HTML element.

I’m not understanding why all of the above would be described as one kind of thing, directives—they don’t seem to logically belong in the same family. So what am I missing? :slight_smile:

One more thing… appInfo.js contains the following:

scope: { info: '=' },

What does that ^ mean/do exactly?