feat: implement InputMediaBuilder

[WingLim]

Create builders subdirectory which other builders can put themselves in it.

InputMediaBuilder methods:

Basic methods:

• add
• build

Advanced methods:

All these methods use Omit to remove type property for each different InputMedia type, so that user can use it more convenient.

• photo
• video
• animation
• audio
• document

Static method:

from method to create a InputMediaBuilder with InputMedia.

• from

Furthermore, it have constructor to initialize with some InputMedia.

It means if you like OOP, you can use new InputMediaBuilder(/** data*/), or you can use InputMediaBuilder.from(/** data*/) if you like FP more.

TODO:

• Documentation for InputMediaBuilder

Close #101

[WingLim]

@KnorpelSenf Plz take a look the code, if it's good for you, then I will write the documentation for it.

[KnorpelSenf]

Thank you so much! I will be able to take a closer look on Wednesday, but perhaps someone else will have a look before me.

[rojvv]

I recommend changing the file name to something simpler (one word), or to input_media_builder.ts. So it is consistent with either the other grammY files or official Deno libraries.

[WingLim]

I think we can rename it to media.ts or input_media.ts, because it's in builders directory, so the builder suffix can be removed.

I prefer the second one, it looks more accurate.

[WingLim]

The static method from comes from #104, and according to #211 (comment), we can use constructor to do this job.

I don't know which one is better?

[WingLim]

The static method from comes from #104, and according to #211 (comment), we can use constructor to do this job.

I don't know which one is better?

I have added them both, in case someone like the other style more.

[KnorpelSenf]

What do you think about also providing something like InputMediaBuilder.Photo and the like? That way, we could create stuff using InputMediaBuilder.Photo.from(...) which can be passed to InputMediaBuilder.from in turn. In addition, it allows for new InputMediaBuilder.Photo() with chained method calls. The main builder could then also support the sub-builders, so that build does not have to be called on all of them.

I am also wondering if there is a better way to create these things than specifying a config object for every entry. Perhaps this is already possible with the idea described above?

[WingLim]

I have a idea about this.

Add a fromType static method which accept 2 params:

1. The media array
2. The real type of InputMedia

Then use a GenericInputMediaBuilder to constraint the type of the specific InputMedia(e.g. InputMediaPhoto) builder:

// This builder can only add `InputMediaPhoto` object.
const builder = InputMediaBuilder.fromType<InputMediaPhoto>(media, "photo");

Let me show you the code to explain it more.

[KnorpelSenf]

Please also add some tests.

[KnorpelSenf]

I now think it is overkill to have a builder for an array. I remember thinking that I would like to abstract that away, but now I believe this would be overkill and take it too far.

I used the rest your changes to create #437. This will subsequently be closed. Thank you anywy for this contribution (and sorry for the long delay)!