Bugzilla – Full Text Bug Listing
| Summary: | [xtend][ui] Hover for feature calls should include implicit receiver / argument | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Sebastian Zarnekow <sebastian.zarnekow> |
| Component: | Xtext | Assignee: | Holger Schill <Holger.Schill> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | Holger.Schill, sven.efftinge |
| Version: | 2.3.0 | Flags: | sven.efftinge:
juno+
|
| Target Milestone: | M5 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
Big +1 We'll try to provide more information in the default hover. It's important to visualize that the feature call is not the declaration but otoh we want to provide easy access to the de-sugared feature call. Hover (comparable to debug hover in JDT): Some Java doc comment More Java doc (scroll bars if long documentation, see Java's view) ------------(I'm a JFace separator)---------------- The unfolded expression (with some simple-to-implement strategy to simplify multi line expressions in parameter lists) --------------------------------------------------- pushed first version to MASTER. Please reopen if I missed something. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |
Currently only the linked function is shown. We should also include the implicitly used information. e.g. extension SomeExtensions def zonk(Thing it) { bar("Foo") } The hover for bar should include this._someExtensions.bar(it, "Foo")