| Summary: | content type id format used in documentation doesn't work | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Rafael Chaves <eclipse> |
| Component: | Doc | Assignee: | Project Inbox <orion.doc-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | mamacdon |
| Version: | unspecified | ||
| Target Milestone: | 0.5 M2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | http://wiki.eclipse.org/Orion/Documentation/Developer_Guide/Plugging_into_the_editor#orion.edit.validator | ||
| Whiteboard: | |||
|
Description
Rafael Chaves
(In reply to comment #0) > It seems the content type id format used in the documentation (many Orion wiki > pages) doesn't work. The docs use a format type.subtype, whereas it seems the > required format is text/subtype. Thanks for the bug. The text.subtype format was a leftover from older versions of Orion (see bug 374991). Several examples in the Wiki docs had not been updated -- these are fixed now. > I could verify that behavior at least in the orion.edit.validator extension > point, not sure about others. About that example, Btw, it seems the right > content type for Javascript (at least on OrionHub) is application/javascript, > not text/javascript. You're correct: the for JavaScript files in Orion is indeed application/javascript. It should work with any extension that lets you provide a 'contentType' property. (In reply to comment #1) > You're correct: the for JavaScript files in Orion is indeed 'The correct *content type ID* for JavaScript files', I mean. |