| Summary: | implement syntax styling for .ejs files | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Grant Gayed <grant_gayed> |
| Component: | Client | Assignee: | Grant Gayed <grant_gayed> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | john.arthorne, ken_walker, simon_kaegi |
| Version: | 5.0 | Flags: | simon_kaegi:
review+
grant_gayed: review? (ken_walker) |
| Target Milestone: | 5.0 RC3 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Grant Gayed
Fixed > 20140220, commit: http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=d359f0350dcf3e859810a20f805badb4d9b52e5a . Also pushed to the R5.0RC2_maintenance branch. So this will only add syntax highlighting right? Other features like content assist and outline will still not work then. I was hoping for a way we could map the extension to an existing content type and get all the features in one go. (In reply to John Arthorne from comment #3) > So this will only add syntax highlighting right? Correct. To get the styling of embedded JS blocks right this type couldn't just be mapped to .html since it doesn't have this notion. I guess our .html content assist could have been reused for files with this type, it just wouldn't be right as-is within embedded JS blocks. |