apache / apache/grails-intellij-plugin
AE at MultiHostRegistrarImpl.doneInjecting() for JavaScript injected into GSP
- Dominant language
- Java
- Stars
- 17
- Forks
- 4
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 4
Description
IntelliJ 14 EAP IU-139.1.20.
I am using Grails' asset:script tag in a GSP page. I tried to inject javascript into the body.
Now I get literally hundreds of errors:
```
Language: JavaScript 1.5;
Host file: Groovy Server Pages file in '/Users//DEVELOPMENT/IOS24/grails-app/views/practice/edit.gsp'
Context element (3340,20294): 'HtmlTag:div'; Ranges: [Shred (3360,3362): XmlText In host range: (3360,3362); PSI range: (0,2), Shred (3547,3549): XmlText In host range: (3547,3549); PSI range: (2,4), Shred (3651,3714): XmlText In host range: (3651,3683); PSI range: (4,6), Shred (3770,3772): XmlText In host range: (3770,3772); PSI range: (6,8), Shred (19938,19940): XmlText In host range: (19938,19940); PSI range: (8,10), Shred (20276,20288): XmlText In host range: (20276,20287); PSI range: (10,12)] (show balloon)
```
Trouble is, I cannot remove this specific inspection. There is no UI for me to do so.
I acknowledge that, in this case, I suspect a bug in the injection code is messing things up because it references 'HtmlTag:div', so having a visual guide may not help anyway...still there should be a UI that reveals these injections.
I am aware that one can have things like @Langauge("Javascript") and the associated "Add @Language annotation or comment if needed" preference setting.
---
*Imported from [IDEA-131086](https://youtrack.jetbrains.com/issue/IDEA-131086) · Type: Exception · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the problem with the Grails asset:script tag in a GSP page using IntelliJ 14 EAP IU-139.1.20, then inspect the MultiHostRegistrarImpl.doneInjecting() exception and the JavaScript injection context shown in the report. Check whether the injected JavaScript inspection can be removed or its injections revealed in the UI; done means the exception and unusable inspection behavior are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100