Ticket #24 (closed defect: fixed)

Opened 14 months ago

Last modified 10 months ago

completion does not work in method bindings

Reported by: stephan Owned by: stephan
Priority: major Milestone: OTDT_1.1.9
Component: content assist Version: 1.1.4
Keywords: Cc:

Description

Within a method binding code completion does not work. Consider these locations:

  • signature
  • guard predicate
  • parameter mapping

Change History

Changed 13 months ago by stephan

  • status changed from new to assigned
  • milestone changed from OTDT_1.1.5 to OTDT_1.1.6

Completion now works in signatures and guard predicates (see r17608, r17621, r17624).

For parameter mappings we first need to implement syntax error recovery. Postponing that part for Release 1.1.6.

Changed 12 months ago by stephan

  • milestone changed from OTDT_1.1.6 to OTDT_1.1.7

Changed 12 months ago by stephan

  • milestone changed from OTDT_1.1.7 to OTDT_1.2.0

Should not block a release.

Changed 10 months ago by mosconi

I encountered the following problems in a 1.1.8 pre-release: - no proposals for callin, even when "<-" is already typed, it offers callouts - completion always creates RHS with full signature, even if LHS is shorthand

Changed 10 months ago by stephan

> no proposals for callin

Did you see the solution in #31? Apparently the UI is not self-explaining. Any suggestions how to improve this?

Changed 10 months ago by stephan

I created a new ticket #97 for those issues regarding the complete generation of method specs.

This ticket remains open for issues of completing individual elements like types as parts of a method spec / guard predicate / parameter mapping.

Changed 10 months ago by stephan

  • milestone changed from OTDT_1.2.0 to OTDT_1.1.9

Given the test in r18161 and the implementation in r18160 I consider this issue fixed.

Changed 10 months ago by stephan

  • status changed from assigned to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.