apply linking logic to inline code spans#4475
Conversation
|
| * HTTP verb (`get`, `put`, `patch`, etc) and handles requests with | ||
| * that method. Note that since 'delete' is a reserved word in | ||
| * JavaScript, delete handles are called `del` instead. | ||
| * A `(event: RequestEvent) => RequestHandlerOutput` function exported from an endpoint that corresponds to an HTTP verb (`get`, `put`, `patch`, etc) and handles requests with that method. Note that since 'delete' is a reserved word in JavaScript, delete handles are called `del` instead. |
There was a problem hiding this comment.
should we make a similar change to the description of Load to make it easier to read sans generics as well?
There was a problem hiding this comment.
sure, we can, i just figured we should get the plumbing in first and then make the actual changes separately (apart from this one for demo purposes) rather than worrying about all the content changes straight away
There was a problem hiding this comment.
I think it's the only other one we might consider to changing from a quick skim though I did earlier, so figured we might as well just get it out of the way. Anyway, this change looks good to me
2 participants
This is a possible solution to #4445 — it makes references to types in inline
<code>spans link to their definitions, and updates theRequestHandlertype accordingly:This seems more scalable/less invasive than the alternative, to me