Make path construction no longer explicitly reference /LQ. (#34)

richardjrossiii · richardjrossiii · commit 76bcc6ca9cfc · 2016-05-09T18:15:58.000-07:00
This hasn't been necessary for a long time with LiveQuery, and should allow this to operate properly behind a reverse proxy or other scenarios where precise path matters. Fixes #33.
diff --git a/Sources/ParseLiveQuery/Client.swift b/Sources/ParseLiveQuery/Client.swift
@@ -51,7 +51,6 @@ public class Client: NSObject {
             fatalError("Server should be a valid URL.")
         }
         components.scheme = components.scheme == "https" ? "wss" : "ws"
-        components.path = "/LQ"
 
         // Simple incrementing generator - can't use ++, that operator is deprecated!
         var currentRequestId = 0

Original file line number	Diff line number	Diff line change
`@@ -51,7 +51,6 @@ public class Client: NSObject {`
`51`	`51`	`fatalError("Server should be a valid URL.")`
`52`	`52`	`}`
`53`	`53`	`components.scheme = components.scheme == "https" ? "wss" : "ws"`
`54`		`- components.path = "/LQ"`
`55`	`54`
`56`	`55`	`// Simple incrementing generator - can't use ++, that operator is deprecated!`
`57`	`56`	`var currentRequestId = 0`