Using typescript I had to go around looking for exports like MelonContext etc. the root package should export these. At some level I also feel like the Melon prefix from these classes should be removed because they are adding stutter to names. But for now I am sticking to the original convention.

Without this pull request, there were be only two response options: json and text. It is necessary to have a res response option to send a simple new Response() object.

There is an error in the exporting statements. Typescript 3.8 introduces new syntax for type-only exports, which are not being used. This pull request will fix the problem.

Hello.

I cloned the latest version of this repository and when I ran bun index.ts there was an error, which is: indirectly exported binding name 'MelonHandler' is not found. The error happens in the latest version because in 0.1.1 and 0.1.0 it works fine.

Thank you.

Currently in the functions ctx.text(statusCode, data) and ctx.json(statusCode, data) has statusCode at the start.

Request

Convert the above functions to:

• ctx.text(statusCode, data) --> ctx.text(data, statusCode, options)
• ctx.json(statusCode, data) --> ctx.json(data, statusCode, options)

And ensure the default response code is 200 if not passed

Action Items

• [ ] Fix Codebase to do so
• [ ] Update readme and relevant docs to reflect the same

This PR contains the following:

• Implementation of MelonContext that allows for:
  • ctx.json()
  • ctx.text()
• Default handler using the app.get("*", (req, ctx) => ctx.text(200, "default handler"))
• Fix for / route being trimmed due to trailing sanitisation

This PR adds the following support:

• Ability to register multiple routers to multiple paths [15f4cc32529402b8210c84490c28fb5f01beaa40]
• Ability to register global and router-specific middlewares [0109d634d7d2354e805713aca250b168ecb59007, dac8114f6b326fe5416e6f15642e257d6cd908a2]
• Introduces a RouterInternalUtility class in 6cdf61118b4b17d002b17abb7f91bdcddc59a112

Notes

Fix: to add a new property private headers: Headers; in Melonpan, which contains all set headers, in order to pass them as a param in all the new Response() objects. So now we just need to call melonpan.cors() to set all the default headers, which are:

[
  ["Access-Control-Allow-Origin", "*"]
  ["Access-Control-Allow-Methods", "POST, GET, OPTIONS"]
  ["Access-Control-Allow-Headers", "X-PINGOTHER, Content-Type"]
  ["Access-Control-Max-Age", "86400"]
]

This error occurs because the Access-Control-Allow-Origin: * header is not present in the new Response() object. In the dev environment we need the headers so the client has not problems in reaching the requested resources. Fix: to add a new property private headers: Headers; in Melonpan, which contains all set headers, in order to pass them as a param in all the new Response() objects. So now we just need to call melonpan.cors() to set all the default headers, which are:

[
  ["Access-Control-Allow-Origin", "*"]
  ["Access-Control-Allow-Methods", "POST, GET, OPTIONS"]
  ["Access-Control-Allow-Headers", "X-PINGOTHER, Content-Type"]
  ["Access-Control-Max-Age", "86400"]
]

I shall make a pull request to fix it.