| Summary: | Content assist doc needs updating | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John Arthorne <john.arthorne> |
| Component: | Doc | Assignee: | John Arthorne <john.arthorne> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 0.4 | ||
| Target Milestone: | 0.4 M2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
0.4 M1 The documentation on content assist is missing details on how to write more complex proposal engines. It should have this detail: The event.proposal may be either a simple string or an object with this shape: { proposal: "[proposal string]", // Actual text of the proposal description: "description", // Optional description to display positions: [{ offset: 10, // Offset of start position of parameter i length: 3 // Length of parameter string for parameter i }], // One object for each parameter; can be null escapePosition: 19 // Offset that caret will be placed at after exiting Linked Mode; can be null } Offsets are relative to the text buffer. /