Locations: Create a convention for creating no-value query parameters about ktor HOT 6 CLOSED

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.

from ktor.

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

from ktor.

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

from ktor.

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)

from ktor.

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

from ktor.

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

from ktor.