https://tip.golang.org/doc/go1.20#errors

Description

It would be great, if you can set status codes with the helper function in the mojito Context. There is often a reason why you don't want to use 200 and it won't look great if ou need to use ctx.Response().WriteHeader(200).
An proposal would be this:

ctx.JSON(http.StatusOK, any)

Additional Context

No response

Code Snippet

No response

Checklist:

• I agree to follow Mojito's Code of Conduct.
• I have checked for existing issues that describe my suggestion prior to opening this one.
• I understand that improperly formatted feature requests reports may be closed without explanation.

Description

Most browsers and other tools expect a favicon to be present on /favicon.ico. To help with this behaviour a utility function to simplify the registration of that endpoint. Optionally a automatic conversion from PNG/JPEG or other image formats to ICO might be a good thing to have.

Additional Context

No response

Code Snippet

package main

import "github.com/go-mojito/mojito"
import "github.com/go-mojito/mojito/handler"

func main() {
  mojito.GET("/", func(ctx mojito.Context) {
    ctx.String("Hello World")
  })
  handler.HandleFavicon()
  mojito.ListenAndServe(":8123")
}

Checklist:

• I agree to follow Mojito's Code of Conduct.
• I have checked for existing issues that describe my suggestion prior to opening this one.
• I understand that improperly formatted feature requests reports may be closed without explanation.

Description

If you use in a handler or middleware ctx.JSON(any); there is no Content-Type: application/json Header

How to Reproduce

func main() {
    mojito.GET("/", func(ctx mojito.Context) {
        ctx.JSON("Hello World")
    })

    mojito.ListenAndServe("127.0.0.1:8123")
}

Expected Behavior

Hello World with the Header Content-Type: application/json

Version

v0.0.14

Code Snippet

package main

import "github.com/go-mojito/mojito"

func main() {
  mojito.GET("/", func(ctx mojito.Context) {
    ctx.JSON("Hello World")
  })
  mojito.ListenAndServe(":8123")
}

Checklist:

• I agree to follow Mojito's Code of Conduct.
• I have checked for existing issues that describe my problem prior to opening this one.
• I understand that improperly formatted bug reports may be closed without explanation.

Description

For larger websites compression would be great to have.

The most common compressions(GZIP and Brotli) should be somehow supported to improve website loading speeds.

Additional Context

TODO:

• Implement new compression middleware
• Test compression middleware with go-mojito.infinytum.co
• Update docs to help users using compression

Code Snippet

package main

import "github.com/go-mojito/mojito"
import compression "github.com/go-mojito/extension-compression"

func main() {
  mojito.GET("/", func(ctx mojito.Context) {
    ctx.String("Hello World")
  })
  mojito.WithMiddleware(compression.GZIP)
  mojito.WithMiddleware(compression.Brotli)
  mojito.ListenAndServe(":8123")
}

Checklist:

• I agree to follow Mojito's Code of Conduct.
• I have checked for existing issues that describe my suggestion prior to opening this one.
• I understand that improperly formatted feature requests reports may be closed without explanation.

The results in our GH Actions Benchmarks seem flaky.

For Example: 3c7481a

Description

If middleware is not registered first it won't be called.

How to Reproduce

1. Create a new mojito project
2. Register middleware after registering routes
3. Middleware will not be called

Expected Behavior

Middleware can be applied at any point in time before ListenAndServe is called

Version

v0.0.14

Code Snippet

package main

import "github.com/go-mojito/mojito"

func main() {
  mojito.GET("/", func(ctx mojito.Context) {
    ctx.String("Hello World")
  })
  mojito.WithMiddleware(middleware.Logging)
  mojito.ListenAndServe(":8123")
}

Checklist:

• I agree to follow Mojito's Code of Conduct.
• I have checked for existing issues that describe my problem prior to opening this one.
• I understand that improperly formatted bug reports may be closed without explanation.

Description

go run main.go

command-line-arguments

./main.go:9:11: ctx.Closed undefined (type "github.com/go-mojito/mojito/websocket".Context has no field or method Closed)

How to Reproduce

1. Run the code snippet

Expected Behavior

Able to compile.

Version

0.0.16

Code Snippet

package main

import "github.com/go-mojito/mojito"
import websocket "github.com/go-mojito/mojito/websocket"

func SomeHandler(ctx websocket.Context) {
    for !ctx.Closed() {
        var msg string
        ctx.Receive(&msg)
        ctx.Send(msg)
    }
}

func main() {
  mojito.GET("/", func(ctx mojito.Context) {
    ctx.String("Hello World")
  })
  mojito.GET("/ws", SomeHandler)
  mojito.ListenAndServe(":8123")
}

Checklist:

• I agree to follow Mojito's Code of Conduct.
• I have checked for existing issues that describe my problem prior to opening this one.
• I understand that improperly formatted bug reports may be closed without explanation.

Description

It would be great to have a helper function or something like that, so you can say the page to reload automaticly if you change a .mojito or .css file while development or debugging

Additional Context

No response

Code Snippet

No response

Checklist:

• I agree to follow Mojito's Code of Conduct.
• I have checked for existing issues that describe my suggestion prior to opening this one.
• I understand that improperly formatted feature requests reports may be closed without explanation.

Description

It would be great, to have the possibility to render / show a custom HTML string and not only a path to a specific file.

Additional Context

No response

Code Snippet

package main

import "github.com/go-mojito/mojito"

func main() {
  mojito.GET("/", func(ctx mojito.RendererContext) {
    ctx.Render(`
      <html>
      <body>
      <h1>Hello World</h1>
      </body>
      </html>
`)
  })
  mojito.ListenAndServe(":8123")
}

Checklist:

• I agree to follow Mojito's Code of Conduct.
• I have checked for existing issues that describe my suggestion prior to opening this one.
• I understand that improperly formatted feature requests reports may be closed without explanation.

.mojito is not a format recognised by most editors. We should document the .mojito format a bit so people know how to use it.