apache / apache/grails-intellij-plugin

Grails Resources not linkable via Editor <asset:* />

Open
#398 0 comments 0 reactions 0 assignees View on GitHub
bug imported-from-youtrack
Dominant language
Java
Stars
17
Forks
4
Avg merge
5d 15h
Merged PRs (30d)
4

Description

# This is a CORE part of Grails and Desperately Needs to be Fixed in IntelliJ

Managing Grails web projects in IntelliJ is a poor experience at best due to the fact there is no easy way to easily navigate between resources.

## Expected behavior

You should be able to click on any grails resource asset tag and the editor will open the resource. For instance: favicon.ico, application.css, application.js and IntelliJ will open the respective source file.

```html

```
## Current behavior

_⚠️ attachment `Screenshot 2024-07-18 at 10.01.40 AM.png` was not included in the export_{width=70%}

## Example Project

git clone

Open website via IntellJ

Open [grails-app/views/layouts/main.gsp](https://github.com/codeconsole/website/blob/master/grails-app/views/layouts/main.gsp) in the editor and notice the resources are not clickable.
```




```
which are all located in the project in the [grails-app/assets](https://github.com/codeconsole/website/tree/master/grails-app/assets) folder

---

*1 attachment(s) referenced here (`Screenshot 2024-07-18 at 10.01.40 AM.png`) are not part of the CSV export.*
*Imported from [IDEA-356545](https://youtrack.jetbrains.com/issue/IDEA-356545) · Type: Bug · Votes: 6*
*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

Clone the linked codeconsole/website example, open it in IntelliJ, and inspect grails-app/views/layouts/main.gsp alongside the files under grails-app/assets. Start by reproducing the non-clickable asset tags; done means the favicon, stylesheet, image, and JavaScript references in that view navigate to their corresponding source files.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.