Minor doc fix: Change misleading sample code in rocket_ws

[mcclure]

Check out

https://api.rocket.rs/master/rocket_ws/

It offers three variants of a single function, at the addresses #[get("/echo?channel")], #[get("/echo?stream")] and #[get("/echo?compose")]. In this case, the ? is only a discriminator; accessing /echo with this sample code directly will give you a 404.

However, using ? in this case is potentially confusing, and did confuse me. I wrote a small app copypasting the channel example and left in the ?channel, assuming it to be "<macro> magic" (as is common in Rocket) and required, and then my app did not work, returning 404s when I queried it, because I'd written the route like #[get("/chat?channel")] and then queried it like http://localhost/chat.

Expected behavior / change in patch

I think you should change the ?s to /s to prevent confusion, and make it clear the intent is one example with three routes rather than three copies of the same example with one route.

Note: It might be an experienced Rocket user would have immediately identified the meaning of the ?channel syntax, but first-contact docs probably should not assume you are an experienced Rocket user.