fix: type in enforceBase64 callable

[brunozoric]

The type in the enforceBase64 callable is not of FastifyReply type but Response from light-my-request package.
I changed code to note that the parameter is a response, not a reply.
Also changed reply to response in the explanation of the enforceBase64 parameter in the docs.

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[Uzlopak]

Why should it be a light my request response?

[brunozoric]

You can see it by the type written here.
LightMyRequestCallback is of type:

type CallbackFunc = (err: Error, response: Response) => void

So response passed into the enforceBase64 callable is of Response type.

[Uzlopak]

If you use .inject() in your typings than you have Response. If you use it in production (not injecting) it should be FastifyReply

[brunozoric]

Code uses .inject() (check here).
And there response is passed into the customBinaryCheck() here.

[Uzlopak]

Ah, makes sense.

[Uzlopak]

LGTM

[Uzlopak]

@adrai
Do we need more reviewers?

[adrai]

@melchor629 ?

[melchor629]

Oh, the change makes a lot of sense.

From my side, LGTM 👍

[adrai]

included in v3.1.1