angular.js - The template format conflict between Beego and AngularJS, how to solve it?

Question

I used the angularjs template in HTML, but in the Controller of beego, I set

this.TplNames = "index.html"

But after running, the information reported by the server is as follows:

I guess it’s because beego parsed it using Go’s own template, so it couldn’t find the variable. But after I set autorender=false, this error still appears, and the front end cannot receive the content of index.html.

Answer 1

https://github.com/astaxie/beego/issues/297 This has been answered by the author.

beego.TemplateLeft = "<<<" 
beego.TemplateRight = ">>>"

Answer 2

beego doesn’t understand
But if it’s a template conflict, just change Angular’s ​​template matching
For example:

app.config ($interpolateProvider) ->
  $interpolateProvider.startSymbol '//'
  $interpolateProvider.endSymbol '//'

Answer 3

If an error is reported on the server side, it must be an error when beego parses the template. Angular's template is pure HTML, because it is a front-end library, so if an error occurs, it will definitely be reported in the browser console. Where exactly something went wrong, you need to take out the code and analyze it for everyone.

Answer 4

There is a Delims function in the template package, which may be what you need. It can change the identifier of the GO parsed template file

Answer 5

The template syntax of golang is very close to the template syntax of angularJS, so it is easy to report errors. Here are two solutions.

• Replace the angularJS template content in the homepage with the golang template tag, for example {{ user.name }} into {{ _user.name }}, and then use golang to render {{ _user.name }} into '{ { user.name }}'. This method can solve the problem, but it is cumbersome to teach.

• Reduce the content on the homepage and try to include the corresponding routing template during design.