Consider making @route optional

[bterlson]

It seems like we could infer a route fragment from the name of the operation. This would make adding a RPC-ish endpoint into an interface much easier.

[timotheeguerin]

I think this is a slightly similar to inferring the verb from the operation name which we decided was a bad idea. At least for now.

@route("/foo")
interface Foo {
   // Does this goes to `/foo` or `/foo/read`. If 1. then when do we decide to use the operation name vs not.
  @get op read(): string;
}

[bterlson]

I would propose /foo/read (everything behaves as if the routeless operation had an @route of the operation name). This rule seems much simpler/less surprising than inferring verbs.

[timotheeguerin]

This however makes this scenario much more verbose

@route("foo/:foo")
interface ResourceEndpoint {
   @route("")
   @get
   op getResource(): T

   @route("")
   @put
   op createOrUpdate(): T

   @route("")
   @put
   op patch(): T

   @route("")
   @put
   op delete(): T
}

[bterlson]

Yeah... that is a good point.