Locations: Create a convention for creating no-value query parameters

[mathiasbn]

If I want a URL to look like this:
/?novalue

The best I can come up with is:

@Location("/") class SomeLocation private constructor(val novalue:String){
    constructor():this("")
}

Which give:
/?novalue=

[orangy]

How about we instead allow to bind routes to paths like /foo/bar?param=1 or /foo/bar?novalue? It would create a query parameter matching selectors at the end of the route chain.

[mathiasbn]

Could you give an example? How would you mark it no value?

[orangy]

Something like @Location("/?novalue&value=1")

[mathiasbn]

Well that could work for some scenarios. It could be annoying if you have 3 possible "novalue", and then need to express 8 different locations. But then again it's difficult to encode everything in the path. "I want novalue with '='", I want without '='", "I want absent optionals to be like novalue", ....

Perhaps it's just better to remove '=' at empty string? Then it's still dynamic.

This is not the most important issue in the world. It's just the representation of the URLs

(Sorry for late reply. Was on vacation)

[stale]

This issue has been automatically marked as stale because it has not had recent activity.

[e5l]

Migrated: https://youtrack.jetbrains.com/issue/KTOR-837