Vikash Kumar

Adding a requirement for cgo reduces compatibility. Many people do prefer to use go without cgo. There is an implementation which does not require cgo, we should prefer that.

We can follow a convention also. If a public folder is present, files in that folder can be accessed by the server.

/remove-lifecycle stale

`pkg/gofr/service/openAI` might be a good place, IMO. But, it should be written in such a way that it gets included only on demand and does not affect all the other...

We can introduce an environment variable LOG_DISABLE_PROBES, which will default to false. But when set to true, will not log these lines.

For gofr's focus on being the framework for Microservices, is cookie a valid use-case? Specially when it changes (adds fields and thus complexity) to the common structs. This does not...