Skip to content

📝 [Proposal]: Retain v2 route signatures #3655

@hiifong

Description

@hiifong

Feature Proposal Description

I would like to keep the route signature from v2, I use routes a lot in v2, it avoids creating variables and is more flexible to use.

Image

Alignment with Express API

v2 route

HTTP RFC Standards Compliance

null

API Stability

yes

Feature Examples

r.Route("/:repo/info/lfs", func(r fiber.Router) {
	r.Use(func(c *fiber.Ctx) error { return nil })
	r.Post("/objects/batch", lfs.Batch)  // Batch download or upload
	r.Get("/objects/:oid", lfs.Download) // Basic downloads
	r.Put("/objects/:oid", lfs.Upload)   // Basic uploads
	r.Post("/verify", lfs.Verify)        // Verification
	r.Route("/locks", func(r fiber.Router) {
		r.Post("/", lfs.Lock)             // Create Lock
		r.Get("/", lfs.ListLock)          // List Locks
		r.Post("/verify", lfs.VerifyLock) // List Locks for Verification
		r.Post("/:id/unlock", lfs.Unlock) // Delete Lock
	})
})

Checklist:

  • I agree to follow Fiber's Code of Conduct.
  • I have searched for existing issues that describe my proposal before opening this one.
  • I understand that a proposal that does not meet these guidelines may be closed without explanation.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions