danog/MadelineProtoDocs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix docs

Browse Source
This commit is contained in:
Daniil Gentili 2018-08-30 20:01:58 +02:00
parent 126051eca8
commit 930cb07d6f
281 changed files with 1615 additions and 225 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/API_docs/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
docs/API_docs/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
docs/API_docs/methods/messages_getPeerDialogs.md
View File

@ -13,7 +13,7 @@ Get dialog info of peers
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peers|Array of [InputDialogPeer](../types/InputDialogPeer.md) | The peers | Yes|
|peers|Array of [Username, chat ID, Update, Message or InputDialogPeer](../types/InputDialogPeer.md) | The peers | Yes|
### Return type: [messages\_PeerDialogs](../types/messages_PeerDialogs.md)

2
docs/API_docs/methods/messages_markDialogUnread.md
View File

@ -14,7 +14,7 @@ Mark dialog as unread
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|unread|[Bool](../types/Bool.md) | Should it be marked or unmarked as read | Optional|
|peer|[InputDialogPeer](../types/InputDialogPeer.md) | The dialog to mark as unread | Yes|
|peer|[Username, chat ID, Update, Message or InputDialogPeer](../types/InputDialogPeer.md) | The dialog to mark as unread | Yes|
### Return type: [Bool](../types/Bool.md)

2
docs/API_docs/methods/messages_reorderPinnedDialogs.md
View File

@ -14,7 +14,7 @@ Reorder pinned dialogs
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|force|[Bool](../types/Bool.md) | Force reordering | Optional|
|order|Array of [InputDialogPeer](../types/InputDialogPeer.md) | New order | Yes|
|order|Array of [Username, chat ID, Update, Message or InputDialogPeer](../types/InputDialogPeer.md) | New order | Yes|
### Return type: [Bool](../types/Bool.md)

2
docs/API_docs/methods/messages_toggleDialogPin.md
View File

@ -14,7 +14,7 @@ Pin or unpin dialog
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|pinned|[Bool](../types/Bool.md) | Pin or unpin the dialog? | Optional|
|peer|[InputDialogPeer](../types/InputDialogPeer.md) | The dialog to pin | Yes|
|peer|[Username, chat ID, Update, Message or InputDialogPeer](../types/InputDialogPeer.md) | The dialog to pin | Yes|
### Return type: [Bool](../types/Bool.md)

2
docs/API_docs/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
docs/API_docs/types/DialogPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$DialogPeer = '@username'; // Username
$DialogPeer = 'me'; // The currently logged-in user
$DialogPeer = 44700; // bot API id (users)
$DialogPeer = -492772765; // bot API id (chats)
$DialogPeer = -10038575794; // bot API id (channels)
$DialogPeer = 'https://t.me/danogentili'; // t.me URLs
$DialogPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$DialogPeer = 'user#44700'; // tg-cli style id (users)
$DialogPeer = 'chat#492772765'; // tg-cli style id (chats)
$DialogPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[dialogPeer](../constructors/dialogPeer.md)

2
docs/API_docs/types/InputChannel.md
View File

@ -29,7 +29,7 @@ $InputChannel = 'chat#492772765'; // tg-cli style id (chats)
$InputChannel = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
docs/API_docs/types/InputDialogPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputDialogPeer = '@username'; // Username
$InputDialogPeer = 'me'; // The currently logged-in user
$InputDialogPeer = 44700; // bot API id (users)
$InputDialogPeer = -492772765; // bot API id (chats)
$InputDialogPeer = -10038575794; // bot API id (channels)
$InputDialogPeer = 'https://t.me/danogentili'; // t.me URLs
$InputDialogPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputDialogPeer = 'user#44700'; // tg-cli style id (users)
$InputDialogPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputDialogPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputDialogPeer](../constructors/inputDialogPeer.md)

24
docs/API_docs/types/InputNotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputNotifyPeer = '@username'; // Username
$InputNotifyPeer = 'me'; // The currently logged-in user
$InputNotifyPeer = 44700; // bot API id (users)
$InputNotifyPeer = -492772765; // bot API id (chats)
$InputNotifyPeer = -10038575794; // bot API id (channels)
$InputNotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$InputNotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputNotifyPeer = 'user#44700'; // tg-cli style id (users)
$InputNotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputNotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputNotifyPeer](../constructors/inputNotifyPeer.md)

2
docs/API_docs/types/InputPeer.md
View File

@ -29,7 +29,7 @@ $InputPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
docs/API_docs/types/InputUser.md
View File

@ -29,7 +29,7 @@ $InputUser = 'chat#492772765'; // tg-cli style id (chats)
$InputUser = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
docs/API_docs/types/NotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$NotifyPeer = '@username'; // Username
$NotifyPeer = 'me'; // The currently logged-in user
$NotifyPeer = 44700; // bot API id (users)
$NotifyPeer = -492772765; // bot API id (chats)
$NotifyPeer = -10038575794; // bot API id (channels)
$NotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$NotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$NotifyPeer = 'user#44700'; // tg-cli style id (users)
$NotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$NotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[notifyPeer](../constructors/notifyPeer.md)

2
docs/API_docs/types/Peer.md
View File

@ -29,7 +29,7 @@ $Peer = 'chat#492772765'; // tg-cli style id (chats)
$Peer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
docs/API_docs/types/User.md
View File

@ -29,7 +29,7 @@ $User = 'chat#492772765'; // tg-cli style id (chats)
$User = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
docs/docs/CALLS.md
View File

@ -124,4 +124,4 @@ while (true) {
}
```
<a href="https://docs.madelineproto.xyz/docs/SECRET_CHATS.html">Next section</a>
<a href="https://docs.madelineproto.xyz/docs/SECRET_CHATS.html">Next section</a>

3
docs/docs/EXCEPTIONS.md
View File

@ -53,8 +53,7 @@ Revision: 63823fc3cc5070bd8a1ebe91e60e1fd583a2f37f
TL Trace (YOU ABSOLUTELY MUST READ THE TEXT BELOW):
PeerHandler.php(327): get_info("dd",false)
TL.php(339): get_info("dd")
['peer']
TL.php(339): get_info("dd")['peer']
While serializing: messages.sendMessage
CallHandler.php(79): serialize_method("messages.sendMessage",{"peer":"@dd","message":"hi"})
APIFactory.php(142): method_call("messages.sendMessage",{"peer":"@dd","message":"hi"},{"datacenter":4})

2
docs/docs/FILES.md
View File

@ -431,4 +431,4 @@ $output_file_name = $MadelineProto->download_to_file(
);
```
<a href="https://docs.madelineproto.xyz/docs/CHAT_INFO.html">Next section</a>
<a href="https://docs.madelineproto.xyz/docs/CHAT_INFO.html">Next section</a>

2
docs/docs/INSTALLATION.md
View File

@ -103,4 +103,4 @@ Then you can require the package by addding the following line to the require se
"danog/madelineproto":"dev-master"
```
<a href="https://docs.madelineproto.xyz/docs/UPDATES.html">Next section</a>
<a href="https://docs.madelineproto.xyz/docs/UPDATES.html">Next section</a>

4
docs/docs/UPDATES.md
View File

@ -302,6 +302,4 @@ The update handling loop is started by the `$MadelineProto->loop()` method, and
To break out of the loop just call `die();`
<a href="https://docs.madelineproto.xyz/docs/SETTINGS.html">Next section</a>
<a href="https://docs.madelineproto.xyz/docs/SETTINGS.html">Next section</a>

1
docs/index.md
View File

@ -74,6 +74,7 @@ Tip: if you receive an error (or nothing), [send us](https://t.me/pwrtelegramgro
* [Long polling (getupdates)](https://docs.madelineproto.xyz/docs/UPDATES.html#long-polling)
* [Callback](https://docs.madelineproto.xyz/docs/UPDATES.html#callback)
* [Callback multithreaded](https://docs.madelineproto.xyz/docs/UPDATES.html#callback-multithreaded)
* [Noop](https://docs.madelineproto.xyz/docs/UPDATES.html#noop)
* [Settings](https://docs.madelineproto.xyz/docs/SETTINGS.html)
* [Getting info about the current user](https://docs.madelineproto.xyz/docs/SELF.html)
* [Exceptions](https://docs.madelineproto.xyz/docs/EXCEPTIONS.html)

2
old_docs/API_docs_v18/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
old_docs/API_docs_v18/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
old_docs/API_docs_v18/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v18/types/InputNotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputNotifyPeer = '@username'; // Username
$InputNotifyPeer = 'me'; // The currently logged-in user
$InputNotifyPeer = 44700; // bot API id (users)
$InputNotifyPeer = -492772765; // bot API id (chats)
$InputNotifyPeer = -10038575794; // bot API id (channels)
$InputNotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$InputNotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputNotifyPeer = 'user#44700'; // tg-cli style id (users)
$InputNotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputNotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputNotifyPeer](../constructors/inputNotifyPeer.md)

2
old_docs/API_docs_v18/types/InputPeer.md
View File

@ -29,7 +29,7 @@ $InputPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v18/types/InputUser.md
View File

@ -29,7 +29,7 @@ $InputUser = 'chat#492772765'; // tg-cli style id (chats)
$InputUser = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v18/types/NotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$NotifyPeer = '@username'; // Username
$NotifyPeer = 'me'; // The currently logged-in user
$NotifyPeer = 44700; // bot API id (users)
$NotifyPeer = -492772765; // bot API id (chats)
$NotifyPeer = -10038575794; // bot API id (channels)
$NotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$NotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$NotifyPeer = 'user#44700'; // tg-cli style id (users)
$NotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$NotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[notifyPeer](../constructors/notifyPeer.md)

2
old_docs/API_docs_v18/types/Peer.md
View File

@ -29,7 +29,7 @@ $Peer = 'chat#492772765'; // tg-cli style id (chats)
$Peer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v18/types/User.md
View File

@ -29,7 +29,7 @@ $User = 'chat#492772765'; // tg-cli style id (chats)
$User = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v23/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
old_docs/API_docs_v23/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
old_docs/API_docs_v23/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v23/types/InputNotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputNotifyPeer = '@username'; // Username
$InputNotifyPeer = 'me'; // The currently logged-in user
$InputNotifyPeer = 44700; // bot API id (users)
$InputNotifyPeer = -492772765; // bot API id (chats)
$InputNotifyPeer = -10038575794; // bot API id (channels)
$InputNotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$InputNotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputNotifyPeer = 'user#44700'; // tg-cli style id (users)
$InputNotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputNotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputNotifyPeer](../constructors/inputNotifyPeer.md)

2
old_docs/API_docs_v23/types/InputPeer.md
View File

@ -29,7 +29,7 @@ $InputPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v23/types/InputUser.md
View File

@ -29,7 +29,7 @@ $InputUser = 'chat#492772765'; // tg-cli style id (chats)
$InputUser = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v23/types/NotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$NotifyPeer = '@username'; // Username
$NotifyPeer = 'me'; // The currently logged-in user
$NotifyPeer = 44700; // bot API id (users)
$NotifyPeer = -492772765; // bot API id (chats)
$NotifyPeer = -10038575794; // bot API id (channels)
$NotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$NotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$NotifyPeer = 'user#44700'; // tg-cli style id (users)
$NotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$NotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[notifyPeer](../constructors/notifyPeer.md)

2
old_docs/API_docs_v23/types/Peer.md
View File

@ -29,7 +29,7 @@ $Peer = 'chat#492772765'; // tg-cli style id (chats)
$Peer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v23/types/User.md
View File

@ -29,7 +29,7 @@ $User = 'chat#492772765'; // tg-cli style id (chats)
$User = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v25/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
old_docs/API_docs_v25/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
old_docs/API_docs_v25/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v25/types/InputNotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputNotifyPeer = '@username'; // Username
$InputNotifyPeer = 'me'; // The currently logged-in user
$InputNotifyPeer = 44700; // bot API id (users)
$InputNotifyPeer = -492772765; // bot API id (chats)
$InputNotifyPeer = -10038575794; // bot API id (channels)
$InputNotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$InputNotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputNotifyPeer = 'user#44700'; // tg-cli style id (users)
$InputNotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputNotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputNotifyPeer](../constructors/inputNotifyPeer.md)

2
old_docs/API_docs_v25/types/InputPeer.md
View File

@ -29,7 +29,7 @@ $InputPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v25/types/InputUser.md
View File

@ -29,7 +29,7 @@ $InputUser = 'chat#492772765'; // tg-cli style id (chats)
$InputUser = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v25/types/NotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$NotifyPeer = '@username'; // Username
$NotifyPeer = 'me'; // The currently logged-in user
$NotifyPeer = 44700; // bot API id (users)
$NotifyPeer = -492772765; // bot API id (chats)
$NotifyPeer = -10038575794; // bot API id (channels)
$NotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$NotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$NotifyPeer = 'user#44700'; // tg-cli style id (users)
$NotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$NotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[notifyPeer](../constructors/notifyPeer.md)

2
old_docs/API_docs_v25/types/Peer.md
View File

@ -29,7 +29,7 @@ $Peer = 'chat#492772765'; // tg-cli style id (chats)
$Peer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v25/types/User.md
View File

@ -29,7 +29,7 @@ $User = 'chat#492772765'; // tg-cli style id (chats)
$User = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v27/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
old_docs/API_docs_v27/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
old_docs/API_docs_v27/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v27/types/InputNotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputNotifyPeer = '@username'; // Username
$InputNotifyPeer = 'me'; // The currently logged-in user
$InputNotifyPeer = 44700; // bot API id (users)
$InputNotifyPeer = -492772765; // bot API id (chats)
$InputNotifyPeer = -10038575794; // bot API id (channels)
$InputNotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$InputNotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputNotifyPeer = 'user#44700'; // tg-cli style id (users)
$InputNotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputNotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputNotifyPeer](../constructors/inputNotifyPeer.md)

2
old_docs/API_docs_v27/types/InputPeer.md
View File

@ -29,7 +29,7 @@ $InputPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v27/types/InputUser.md
View File

@ -29,7 +29,7 @@ $InputUser = 'chat#492772765'; // tg-cli style id (chats)
$InputUser = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v27/types/NotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$NotifyPeer = '@username'; // Username
$NotifyPeer = 'me'; // The currently logged-in user
$NotifyPeer = 44700; // bot API id (users)
$NotifyPeer = -492772765; // bot API id (chats)
$NotifyPeer = -10038575794; // bot API id (channels)
$NotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$NotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$NotifyPeer = 'user#44700'; // tg-cli style id (users)
$NotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$NotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[notifyPeer](../constructors/notifyPeer.md)

2
old_docs/API_docs_v27/types/Peer.md
View File

@ -29,7 +29,7 @@ $Peer = 'chat#492772765'; // tg-cli style id (chats)
$Peer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v27/types/User.md
View File

@ -29,7 +29,7 @@ $User = 'chat#492772765'; // tg-cli style id (chats)
$User = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v33/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
old_docs/API_docs_v33/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
old_docs/API_docs_v33/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v33/types/InputNotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputNotifyPeer = '@username'; // Username
$InputNotifyPeer = 'me'; // The currently logged-in user
$InputNotifyPeer = 44700; // bot API id (users)
$InputNotifyPeer = -492772765; // bot API id (chats)
$InputNotifyPeer = -10038575794; // bot API id (channels)
$InputNotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$InputNotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputNotifyPeer = 'user#44700'; // tg-cli style id (users)
$InputNotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputNotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputNotifyPeer](../constructors/inputNotifyPeer.md)

2
old_docs/API_docs_v33/types/InputPeer.md
View File

@ -29,7 +29,7 @@ $InputPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v33/types/InputUser.md
View File

@ -29,7 +29,7 @@ $InputUser = 'chat#492772765'; // tg-cli style id (chats)
$InputUser = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v33/types/NotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$NotifyPeer = '@username'; // Username
$NotifyPeer = 'me'; // The currently logged-in user
$NotifyPeer = 44700; // bot API id (users)
$NotifyPeer = -492772765; // bot API id (chats)
$NotifyPeer = -10038575794; // bot API id (channels)
$NotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$NotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$NotifyPeer = 'user#44700'; // tg-cli style id (users)
$NotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$NotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[notifyPeer](../constructors/notifyPeer.md)

2
old_docs/API_docs_v33/types/Peer.md
View File

@ -29,7 +29,7 @@ $Peer = 'chat#492772765'; // tg-cli style id (chats)
$Peer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v33/types/User.md
View File

@ -29,7 +29,7 @@ $User = 'chat#492772765'; // tg-cli style id (chats)
$User = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v38/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
old_docs/API_docs_v38/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
old_docs/API_docs_v38/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v38/types/InputChannel.md
View File

@ -29,7 +29,7 @@ $InputChannel = 'chat#492772765'; // tg-cli style id (chats)
$InputChannel = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v38/types/InputNotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputNotifyPeer = '@username'; // Username
$InputNotifyPeer = 'me'; // The currently logged-in user
$InputNotifyPeer = 44700; // bot API id (users)
$InputNotifyPeer = -492772765; // bot API id (chats)
$InputNotifyPeer = -10038575794; // bot API id (channels)
$InputNotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$InputNotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputNotifyPeer = 'user#44700'; // tg-cli style id (users)
$InputNotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputNotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputNotifyPeer](../constructors/inputNotifyPeer.md)

2
old_docs/API_docs_v38/types/InputPeer.md
View File

@ -29,7 +29,7 @@ $InputPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v38/types/InputUser.md
View File

@ -29,7 +29,7 @@ $InputUser = 'chat#492772765'; // tg-cli style id (chats)
$InputUser = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v38/types/NotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$NotifyPeer = '@username'; // Username
$NotifyPeer = 'me'; // The currently logged-in user
$NotifyPeer = 44700; // bot API id (users)
$NotifyPeer = -492772765; // bot API id (chats)
$NotifyPeer = -10038575794; // bot API id (channels)
$NotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$NotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$NotifyPeer = 'user#44700'; // tg-cli style id (users)
$NotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$NotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[notifyPeer](../constructors/notifyPeer.md)

2
old_docs/API_docs_v38/types/Peer.md
View File

@ -29,7 +29,7 @@ $Peer = 'chat#492772765'; // tg-cli style id (chats)
$Peer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v38/types/User.md
View File

@ -29,7 +29,7 @@ $User = 'chat#492772765'; // tg-cli style id (chats)
$User = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v40/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
old_docs/API_docs_v40/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
old_docs/API_docs_v40/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v40/types/InputNotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputNotifyPeer = '@username'; // Username
$InputNotifyPeer = 'me'; // The currently logged-in user
$InputNotifyPeer = 44700; // bot API id (users)
$InputNotifyPeer = -492772765; // bot API id (chats)
$InputNotifyPeer = -10038575794; // bot API id (channels)
$InputNotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$InputNotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputNotifyPeer = 'user#44700'; // tg-cli style id (users)
$InputNotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputNotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputNotifyPeer](../constructors/inputNotifyPeer.md)

2
old_docs/API_docs_v40/types/InputPeer.md
View File

@ -29,7 +29,7 @@ $InputPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v40/types/InputUser.md
View File

@ -29,7 +29,7 @@ $InputUser = 'chat#492772765'; // tg-cli style id (chats)
$InputUser = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v40/types/NotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$NotifyPeer = '@username'; // Username
$NotifyPeer = 'me'; // The currently logged-in user
$NotifyPeer = 44700; // bot API id (users)
$NotifyPeer = -492772765; // bot API id (chats)
$NotifyPeer = -10038575794; // bot API id (channels)
$NotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$NotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$NotifyPeer = 'user#44700'; // tg-cli style id (users)
$NotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$NotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[notifyPeer](../constructors/notifyPeer.md)

2
old_docs/API_docs_v40/types/Peer.md
View File

@ -29,7 +29,7 @@ $Peer = 'chat#492772765'; // tg-cli style id (chats)
$Peer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v40/types/User.md
View File

@ -29,7 +29,7 @@ $User = 'chat#492772765'; // tg-cli style id (chats)
$User = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v41/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
old_docs/API_docs_v41/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
old_docs/API_docs_v41/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v41/types/InputChannel.md
View File

@ -29,7 +29,7 @@ $InputChannel = 'chat#492772765'; // tg-cli style id (chats)
$InputChannel = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v41/types/InputNotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$InputNotifyPeer = '@username'; // Username
$InputNotifyPeer = 'me'; // The currently logged-in user
$InputNotifyPeer = 44700; // bot API id (users)
$InputNotifyPeer = -492772765; // bot API id (chats)
$InputNotifyPeer = -10038575794; // bot API id (channels)
$InputNotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$InputNotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$InputNotifyPeer = 'user#44700'; // tg-cli style id (users)
$InputNotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputNotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[inputNotifyPeer](../constructors/inputNotifyPeer.md)

2
old_docs/API_docs_v41/types/InputPeer.md
View File

@ -29,7 +29,7 @@ $InputPeer = 'chat#492772765'; // tg-cli style id (chats)
$InputPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v41/types/InputUser.md
View File

@ -29,7 +29,7 @@ $InputUser = 'chat#492772765'; // tg-cli style id (chats)
$InputUser = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

24
old_docs/API_docs_v41/types/NotifyPeer.md
View File

@ -8,6 +8,30 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
You can directly provide the [Update](Update.md) or [Message](Message.md) object here, MadelineProto will automatically extract the destination chat id.
The following syntaxes can also be used:
```
$NotifyPeer = '@username'; // Username
$NotifyPeer = 'me'; // The currently logged-in user
$NotifyPeer = 44700; // bot API id (users)
$NotifyPeer = -492772765; // bot API id (chats)
$NotifyPeer = -10038575794; // bot API id (channels)
$NotifyPeer = 'https://t.me/danogentili'; // t.me URLs
$NotifyPeer = 'https://t.me/joinchat/asfln1-21fa_'; // t.me invite links
$NotifyPeer = 'user#44700'; // tg-cli style id (users)
$NotifyPeer = 'chat#492772765'; // tg-cli style id (chats)
$NotifyPeer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):
[notifyPeer](../constructors/notifyPeer.md)

2
old_docs/API_docs_v41/types/Peer.md
View File

@ -29,7 +29,7 @@ $Peer = 'chat#492772765'; // tg-cli style id (chats)
$Peer = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v41/types/User.md
View File

@ -29,7 +29,7 @@ $User = 'chat#492772765'; // tg-cli style id (chats)
$User = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v42/methods/account_getNotifySettings.md
View File

@ -13,7 +13,7 @@ Get notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | Notification source | Yes|
### Return type: [PeerNotifySettings](../types/PeerNotifySettings.md)

2
old_docs/API_docs_v42/methods/account_updateNotifySettings.md
View File

@ -13,7 +13,7 @@ Change notification settings
| Name | Type | Description | Required |
|----------|---------------|-------------|----------|
|peer|[InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|peer|[Username, chat ID, Update, Message or InputNotifyPeer](../types/InputNotifyPeer.md) | The peers to which the notification settings should be applied | Yes|
|settings|[InputPeerNotifySettings](../types/InputPeerNotifySettings.md) | Notification settings | Yes|

2
old_docs/API_docs_v42/types/Chat.md
View File

@ -29,7 +29,7 @@ $Chat = 'chat#492772765'; // tg-cli style id (chats)
$Chat = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

2
old_docs/API_docs_v42/types/InputChannel.md
View File

@ -29,7 +29,7 @@ $InputChannel = 'chat#492772765'; // tg-cli style id (chats)
$InputChannel = 'channel#38575794'; // tg-cli style id (channels)
```
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), or a [Chat](Chat.md) object can also be used.
A [Chat](Chat.md), a [User](User.md), an [InputPeer](InputPeer.md), an [InputDialogPeer](InputDialogPeer.md), an [InputNotifyPeer](InputNotifyPeer.md), an [InputUser](InputUser.md), an [InputChannel](InputChannel.md), a [Peer](Peer.md), an [DialogPeer](DialogPeer.md), [NotifyPeer](NotifyPeer.md), or a [Chat](Chat.md) object can also be used.
### Possible values (constructors):

Some files were not shown because too many files have changed in this diff Show More