Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

docs($compileProvider): more information on debugInfoEnabled #16154

Closed
wants to merge 2 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions src/ng/compile.js
Original file line number Diff line number Diff line change
Expand Up @@ -1387,7 +1387,12 @@ function $CompileProvider($provide, $$sanitizeUriProvider) {
* binding information and a reference to the current scope on to DOM elements.
* If enabled, the compiler will add the following to DOM elements that have been bound to the scope
* * `ng-binding` CSS class
* * `ng-scope` and `ng-isolated-scope` CSS classes
* * `$binding` data property containing an array of the binding expressions
* * `$scope`, `$isolateScope` or `$isolateScopeNoTemplate` data properties which are accessable via the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is too much implementation details imo. Please change to something like:

Data properties used by the {@link angular.element#methods scope()/isolateScope() methods} to return the element's scope.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is a very good point

* {@link angular.element#methods `scope()` or `isolateScope()` methods}.
* * Placeholder comments will contain information about what directive and binding caused the placeholder.
* E.g. `<!-- ngIf: shouldShow() -->`
*
* You may want to disable this in production for a significant performance boost. See
* {@link guide/production#disabling-debug-data Disabling Debug Data} for more.
Expand Down