67a2fe494a
Fix up compile operation kind
...
- `key.compile_operation` instead of `key.compileoperation`
- Make the operation kind optional (nothing emitted for perform sema)
2020-05-18 13:18:40 -04:00
40759df737
[SourceKit] Include operation kind in compile notifications
...
- Compile will start / did finish now includes the operation
kind (perform sema or code complete).
- See also
https://forums.swift.org/t/sourcekit-lsp-file-status-ux/35947
2020-05-15 17:16:30 -04:00
bd21fb4e65
Merge pull request #26205 from gmittert/YetAnotherPathChange
...
Handle Windows Paths in CompileNotifications Tests
2019-07-18 11:01:05 -07:00
44cd3ff33d
Handle Windows Paths in CompileNotifications Tests
...
On Windows, JSON output creates paths with `\\` separators, so pass
--enable-yaml-compatibility to handle it properly.
2019-07-17 18:38:29 -07:00
f863c93183
[Windows] Fix SourceKit/CompileNotifications/code-completion.swift
...
When Windows normalizes paths, it prefixes them with \\?\. Fix the regex
to allow this.
2019-07-17 14:40:22 -07:00
79d641d89b
[sourcekit] Add optional compile notifications
...
When enabled, send a notification before/after every "compilation",
which for now means `performSema`. This piggy-backs and modifies some
existing code that we had for "tracing" operations in sourcekitd that
unfortunately was untested. At least now some of the basic parts are
tested via the new notifications.
Part of rdar://38438512
2018-03-29 14:59:30 -07:00
David Goldman
Ben Langmuir
Gwen Mittertreiner