ng-directives | I am cleaning up this repository and listing the directives

As @Ian Kemp said in the comments i had to add a reference to the dll. Normaly i work with rider where this happens automaticaly.

Technically, the example you've given does compile, but it fails to link. The issue is the line

[namespace.udir]/2 A using-directive specifies that the names in the nominated namespace can be used in the scope in which the using-directive appears after the using-directive. During unqualified name lookup (6.4.1), the names appear as if they were declared in the nearest enclosing namespace which contains both the using-directive and the nominated namespace. [ Note: In this context, “contains” means “contains directly or indirectly”. —end note ]

Emphasis mine. In prog1, that nearest enclosing namespace is the global namespace, and A::Detail is found before ::Detail. In prog2, that nearest enclosing namespace is A, and so the name lookup finds two different namespaces both named A::Detail.

If the @auth directive shown is applied to a type, that type could also have another directive applied to it that adds fields to the type. For example, imagine an @id directive that added an id field to whatever type it was applied to. If the @id directive directive is applied after the @auth directive, the id field's resolver would never be modified by the @auth directive like all the other fields were. The directives are applied in the order they appear in the type definition, so it's easy enough to avoid this scenario but it is something to be aware of if you make extensive use of directives.

Make sure that you always import akka.http.scaladsl.server.Directives._ or extend directives like this in your class: class MyRoutes extends Directives {. This brings into scope everything you need.

We'll work on samples to include all imports and link back to the source code so you can browse it in context in the near future.

It seems that it is a bug of gcc. According to the C++ 20 Standard (6.3.7 Class scope)

2 A name N used in a class S shall refer to the same declaration in its context and when re-evaluated in the completed scope of S. No diagnostic is required for a violation of this rule.

In this case

Is ng-repeat somehow different?

The ng-repeat adds and destroys DOM based on data. The .find operation does not find the elements because they have not been yet added to the DOM.

Add the event handler in a directive which is invoked when the framework adds the element to the DOM:

You can do something like this:

Yes, this is the directive you are looking for, and I agree - the official documentation is a bit hard to grasp on.

Here is how an endpoint with logRequestResult would look like: