HaxeFoundation / HaxeFoundation/haxe
Completion on first structure field should not fallback to top-level
- Dominant language
- Haxe
- Stars
- 6.9k
- Forks
- 715
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 11
Description
```haxe
typedef Foo = {
?someField:String,
?secondField:Int,
}
class Main {
static function main() {
final foo:Foo = {
s|
secondField: 10,
}
}
}
```
4.2.5 (`secondField` can be detected and filtered from completion on vshaxe side, i think, fields after first comma are parsed and filtered already):
Upd: cannot reproduce this result anymore, my mistake, happens only if you trigger completion first and then write `s`
dev:
Contributor guide
Research direction
Start with the supplied Haxe snippet and reproduce completion after triggering completion first, then typing `s`; compare that behavior with the result after typing `s` before triggering completion. Done means completion on the first structure field remains scoped to the structure fields rather than falling back to top-level suggestions.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100