En/error fields

[Umang01-hash]

Pull Request Template

Description:

• Allows users to add more fields in their error response.

Example

Checklist:

• I have formatted my code using goimport and golangci-lint.
• All new code is covered by unit tests.
• This PR does not decrease the overall code coverage.
• I have reviewed the code comments and documentation for clarity.

Thank you for your contribution!

[coolwednesday]

@Umang01-hash , when we send an empty struct, ideally we should get a 500 status code and some details(that are hardcoded and do not need to be initialised) in the error response . However in such case it returns a 200 status code ...a new field status as 500 and status as Error. Seems a bit weird.

Also whenever the status code is not set, can we handle to return 500 ? As in current case it causes panic in writeHeader.

[Copilot]

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

docs/advanced-guide/gofr-errors/page.md:73

• There is a naming inconsistency between 'ResponseMarshaler' defined in the docs and 'ResponseMarshaller' used in the code. Consider aligning the interface naming for clarity.

type ResponseMarshaler interface {