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

Resetstate docs

Browse Source
This commit is contained in:
Daniil Gentili 2019-06-05 10:51:09 +02:00
parent 6fe646f4a2
commit b6ca39b88e
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/docs/UPDATES.md
View File

@ -11,7 +11,7 @@ Update handling can be done in different ways:
* [Multi-account: Async Combined Event driven update handling](#async-combined-event-driven) * [Multi-account: Async Combined Event driven update handling](#async-combined-event-driven)
* [Async Callback](#async-callback) * [Async Callback](#async-callback)
* [Noop (default)](#noop) * [Noop (default)](#noop)
* [Fetch all updates from the beginning](#fetch-all-updates-from-the-beginning)
``` ```
@ -246,4 +246,12 @@ $MadelineProto->setNoop();
When an [Update](https://docs.madelineproto.xyz/API_docs/types/Update.html) is received, nothing is done. This is useful if you need to populate the internal peer database with peers to avoid `This peer is not present in the internal peer database errors`, but don't need to handle updates. When an [Update](https://docs.madelineproto.xyz/API_docs/types/Update.html) is received, nothing is done. This is useful if you need to populate the internal peer database with peers to avoid `This peer is not present in the internal peer database errors`, but don't need to handle updates.
This is the default. This is the default.
## Fetch all updates from the beginning
You can use the `resetUpdateState` method to reset the update state and fetch all updates from the beginning:
```php
$MadelineProto->resetUpdateState();
```
<a href="https://docs.madelineproto.xyz/docs/SETTINGS.html">Next section</a> <a href="https://docs.madelineproto.xyz/docs/SETTINGS.html">Next section</a>