Optional route segments

[carl-berg]

Would be nice to be able to insert a route segment optionally. Consider this api

[BaseLocation("api/{version}")]
public interface IUserApi
{
    [Get("user")]
    Task<UserResult> GetUser([Header("Authorization")] string bearer);
}

If version=v1 you would get api/v1/user
... but if version="", you would get api//user so it would be nice if that could be handled somehow by WebAnchor

[mattiasnordqvist]

Are we happy with just repeating execution of Replace("//", "/") until there's no "//" left, or will that break anything?

[carl-berg]

It could potentially break something i guess if someone is actually using // on purpose in a url, but is that even valid?

[mattiasnordqvist]

my browser accepts it. Let's just make it opt-in

[mattiasnordqvist]

this issue kind of also raises the question about what should happen if a route segment value is null.

[mattiasnordqvist]

Also, about normalizing urls. We could implement a lot of stuff:
https://en.wikipedia.org/wiki/URI_normalization

[mattiasnordqvist]

There ya go!

[mattiasnordqvist]

@all-contributors please add @carl-berg for bug reports

[allcontributors]

@mattiasnordqvist

I've put up a pull request to add @carl-berg! 🎉