{"action":"created","issue":{"url":"https://api.github.com/repos/HaxeFoundation/haxe/issues/7173","repository_url":"https://api.github.com/repos/HaxeFoundation/haxe","labels_url":"https://api.github.com/repos/HaxeFoundation/haxe/issues/7173/labels{/name}","comments_url":"https://api.github.com/repos/HaxeFoundation/haxe/issues/7173/comments","events_url":"https://api.github.com/repos/HaxeFoundation/haxe/issues/7173/events","html_url":"https://github.com/HaxeFoundation/haxe/issues/7173","id":331206306,"node_id":"MDU6SXNzdWUzMzEyMDYzMDY=","number":7173,"title":"[display] new protocol should return file name paths with proper casing on Windows","user":{"login":"Gama11","id":2620907,"node_id":"MDQ6VXNlcjI2MjA5MDc=","avatar_url":"https://avatars0.githubusercontent.com/u/2620907?v=4","gravatar_id":"","url":"https://api.github.com/users/Gama11","html_url":"https://github.com/Gama11","followers_url":"https://api.github.com/users/Gama11/followers","following_url":"https://api.github.com/users/Gama11/following{/other_user}","gists_url":"https://api.github.com/users/Gama11/gists{/gist_id}","starred_url":"https://api.github.com/users/Gama11/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Gama11/subscriptions","organizations_url":"https://api.github.com/users/Gama11/orgs","repos_url":"https://api.github.com/users/Gama11/repos","events_url":"https://api.github.com/users/Gama11/events{/privacy}","received_events_url":"https://api.github.com/users/Gama11/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-11T14:11:21Z","updated_at":"2018-06-11T14:17:10Z","closed_at":null,"author_association":"MEMBER","body":"The file paths returned by display requests on Windows has traditionally always been all-lowercase (rather than what they actually are on the file system). In vshaxe, we need a very ugly workaround for this to avoid files getting opened twice with different cases:\r\n\r\nhttps://github.com/vshaxe/haxe-languageserver/blob/970219041d33cf3fe44446f7a0fd60b8f7c8e9be/src/haxeLanguageServer/HaxePosition.hx#L71\r\n\r\n![](https://i.imgur.com/XfYfUdo.png)\r\n\r\nHaxe would probably need something similar, but it could maybe be more optimized than whatever vshaxe currently does. We should look into fixing this at least for the new display protocol. I'm not sure if editors other than VSCode have this issue, but it seems quite likely that some would.\r\n"},"comment":{"url":"https://api.github.com/repos/HaxeFoundation/haxe/issues/comments/396259314","html_url":"https://github.com/HaxeFoundation/haxe/issues/7173#issuecomment-396259314","issue_url":"https://api.github.com/repos/HaxeFoundation/haxe/issues/7173","id":396259314,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NjI1OTMxNA==","user":{"login":"nadako","id":49749,"node_id":"MDQ6VXNlcjQ5NzQ5","avatar_url":"https://avatars0.githubusercontent.com/u/49749?v=4","gravatar_id":"","url":"https://api.github.com/users/nadako","html_url":"https://github.com/nadako","followers_url":"https://api.github.com/users/nadako/followers","following_url":"https://api.github.com/users/nadako/following{/other_user}","gists_url":"https://api.github.com/users/nadako/gists{/gist_id}","starred_url":"https://api.github.com/users/nadako/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nadako/subscriptions","organizations_url":"https://api.github.com/users/nadako/orgs","repos_url":"https://api.github.com/users/nadako/repos","events_url":"https://api.github.com/users/nadako/events{/privacy}","received_events_url":"https://api.github.com/users/nadako/received_events","type":"User","site_admin":false},"created_at":"2018-06-11T14:17:10Z","updated_at":"2018-06-11T14:17:10Z","author_association":"MEMBER","body":"`Path.get_real_path` does this and is implemented in C so should be quite fast (it still does FS queries tho)."}}
{"actor":{"display_login":"nadako"}}