IntelliJ 13在内联脚本中抱怨'未转义的xml字符' [英] IntelliJ 13 complaining about an 'unescaped xml character' in inline script
本文介绍了IntelliJ 13在内联脚本中抱怨'未转义的xml字符'的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
谁做错了我或它?
<!DOCTYPE html>
< html>
< head>
< script type =text / ng-templateid =_ template / company.inline>
< g:render template =/ shared / header/>
< g:render template =/ shared / nav/>
< section id =content>
< section class =main padderapp-view-segment =1>< / section>
< / section>
< / script>
那么这是一个有效的xml ?我不需要用cdata或其他东西来包装它?
解决方案
这是最近EAP版本中的一个已知错误( http://youtrack.jetbrains.com/issue/WEB-9833 )。它现在已经修复,因此应该很快出现在下一个EAP版本中。
IntelliJ's inspector is underlining the body of the script tag. Who is doing something wrong me or it?
<!DOCTYPE html>
<html>
<head>
<script type="text/ng-template" id="_template/company.inline">
<g:render template="/shared/header"/>
<g:render template="/shared/nav"/>
<section id="content">
<section class="main padder" app-view-segment="1"></section>
</section>
</script>
So is this a valid xml? And I do not required to wrap this with cdata or something else?
解决方案
It is a known bug in the lasts EAP versions (http://youtrack.jetbrains.com/issue/WEB-9833). It is fixed now so it should appears soon in a next EAP version.
这篇关于IntelliJ 13在内联脚本中抱怨'未转义的xml字符'的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文