The problem I find is that it Frontend
has an application information bar (php) that returns information about the execution of the Backend
.
Within this information, there are certain configuration values of this style:
'config/autoload/{{,*.}global,{,*.}local}.php'
In addition to other similar ones that belong to routers and so on.
The issue is that it AngularJs
tries to interpret this information and throws errors in the console. And it becomes a bit difficult to track other bugs during development.
He html
has a basic structure:
<html ng-app="App">
<head></head>
<body ng-controller="AngularController">
<header></header>
<main></main>
<footer></footer>
<!-- Aquí se cargan los datos del backend -->
</body>
</html>
With this background I return again to the title of the question.
Is it possible to narrow the scope of a controller in AngularJs to avoid the part of the html that causes the errors?
For example, that only act on the label <main>
.
Or on the contrary, to avoid acting on a specific part of the html
.
Yes, by putting the ng-controller in the tag where you want it to act, if you put it in main, its scope will be the main div:
Edit my Answer, I think you could use ng-non-bindable on the tag(s) you want Angular not to interpret.
Font