Accept default update types sent by Telegram, if not explicitly specified.

Author: noplanman

README.md

@@ -341,30 +341,19 @@ $telegram->useGetUpdatesWithoutDatabase();
 
 ## Filter Update
 
-Update processing can be allowed or denied by defining a custom update filter.
+:exclamation: Note that by default, Telegram will send any new update types that may be added in the future. This may cause commands that don't take this into account to break!
 
-Let's say we only want to allow messages from a user with ID `428`, we can do the following before handling the request:
+It is suggested that you specifically define which update types your bot can receive and handle correctly.
 
-```php
-$telegram->setUpdateFilter(function (Update $update, Telegram $telegram, &$reason = 'Update denied by update_filter') {
-    $user_id = $update->getMessage()->getFrom()->getId();
-    if ($user_id === 428) {
-        return true;
-    }
-
-    $reason = "Invalid user with ID {$user_id}";
-    return false;
-});
-```
-
-The reason for denying an update can be defined with the `$reason` parameter. This text gets written to the debug log.
-
-Alternatively, you can define which update types are handled by your bot, by defining them when setting the [webhook](#webhook-installation) or passing an array of allowed types when using [getUpdates](#getupdates-installation).
+You can define which update types are sent to your bot by defining them when setting the [webhook](#webhook-installation) or passing an array of allowed types when using [getUpdates](#getupdates-installation).
 
 ```php
 use Longman\TelegramBot\Entities\Update;
 
-// Define the list of allowed Update types here.
+// For all update types currently implemented in this library:
+// $allowed_updates = Update::getUpdateTypes();
+
+// Define the list of allowed Update types manually:
 $allowed_updates = [
     Update::TYPE_MESSAGE,
     Update::TYPE_CHANNEL_POST,
@@ -378,6 +367,24 @@ $telegram->setWebhook($hook_url, ['allowed_updates' => $allowed_updates]);
 $telegram->handleGetUpdates(['allowed_updates' => $allowed_updates]);
 ```
 
+Alternatively, Update processing can be allowed or denied by defining a custom update filter.
+
+Let's say we only want to allow messages from a user with ID `428`, we can do the following before handling the request:
+
+```php
+$telegram->setUpdateFilter(function (Update $update, Telegram $telegram, &$reason = 'Update denied by update_filter') {
+    $user_id = $update->getMessage()->getFrom()->getId();
+    if ($user_id === 428) {
+        return true;
+    }
+
+    $reason = "Invalid user with ID {$user_id}";
+    return false;
+});
+```
+
+The reason for denying an update can be defined with the `$reason` parameter. This text gets written to the debug log.
+
 ## Support
 
 ### Types

src/Telegram.php

@@ -415,9 +415,11 @@ public function handleGetUpdates($data = null, ?int $timeout = null): ServerResp
             );
         }
 
-        $offset          = 0;
-        $limit           = null;
-        $allowed_updates = null;
+        $offset = 0;
+        $limit  = null;
+
+        // By default, get update types sent by Telegram.
+        $allowed_updates = [];
 
         // @todo Backwards compatibility for old signature, remove in next version.
         if (!is_array($data)) {
@@ -434,11 +436,6 @@ public function handleGetUpdates($data = null, ?int $timeout = null): ServerResp
             $allowed_updates = $data['allowed_updates'] ?? $allowed_updates;
         }
 
-        // By default, allow ALL known update types.
-        if ($allowed_updates === null) {
-            $allowed_updates = Update::getUpdateTypes();
-        }
-
         // Take custom input into account.
         if ($custom_input = $this->getCustomInput()) {
             try {