Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add examples for every feature #166

Open
tdakkota opened this issue Feb 28, 2021 · 11 comments
Open

doc: add examples for every feature #166

tdakkota opened this issue Feb 28, 2021 · 11 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request epic Feature that is too big for single issue good first issue Good for newcomers

Comments

@tdakkota
Copy link
Member

For now, gotd have a lot badly documented features and helpers, like uploader package.

@tdakkota tdakkota added documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers epic Feature that is too big for single issue labels Feb 28, 2021
@paskal
Copy link

paskal commented Jul 11, 2021

The project would benefit greatly from an examples folder with different scenarios like big file upload or examples per package to be available in the module documentation.

ernado added a commit that referenced this issue Jul 11, 2021
Add #166 as current primary focus
@ernado
Copy link
Member

ernado commented Jul 11, 2021

I've added documentation as current focus to roadmap.

Until then, feel free to ask questions in telegram groups, we have both English and Russian support channels.
Also there are upload in cli, so you can see https://github.com/gotd/cli/blob/ecd58c4e716de86cf8c37520989a8bb3391fe783/cmd/tg/upload.go#L162-L170 for reference for uploads.

@ernado ernado pinned this issue Jul 11, 2021
ernado added a commit that referenced this issue Jul 11, 2021
This was referenced Jul 11, 2021
@lilien1010
Copy link

We definitely need an example of:
user login by code with session storage in file
user reconnect with the previous session.
user send message to a channel.

@Vponed
Copy link

Vponed commented Jan 17, 2022

We definitely need an example of: user login by code with session storage in file user reconnect with the previous session. user send message to a channel.

Очень прошу пример с входом по коду и сохранением в сессию

@AlexanderMatveev
Copy link

AlexanderMatveev commented Jun 1, 2022

Please add example of ChannelsGetParticipants method usage

@suntong
Copy link

suntong commented Mar 13, 2023

Очень прошу пример с входом по коду и сохранением в сессию

Translate in English: "I want to ask for an example with entering by code and saving to the session"

@suntong
Copy link

suntong commented Mar 13, 2023

We definitely need an example of: user login by code with session storage in file user reconnect with the previous session. user send message to a channel.

Yes, and further than that,

  • reply to a picture / video message with key phrase like "save" and it'll save the refered picture / video.

@biji
Copy link

biji commented Mar 20, 2023

Is there any example how to add contact (phone number)?

Thanks

@suntong
Copy link

suntong commented Mar 20, 2023

Is there any example how to add contact (phone number)?

Don't do that -- it's a surefire invitation to get your account banned in lightning speed.

@biji
Copy link

biji commented Mar 20, 2023

Most of recipients already added server's phone in their contact. Recipients to be resolved , sender need to add contact first

@biji
Copy link

biji commented Mar 27, 2023

Any clue, how to get peer's phone number inside:

dispatcher.OnNewMessage(func(ctx context.Context, entities tg.Entities, update *tg.UpdateNewMessage)  

thanks

@ernado ernado unpinned this issue Apr 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request epic Feature that is too big for single issue good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

8 participants