-
-
Notifications
You must be signed in to change notification settings - Fork 950
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1397 from php-telegram-bot/refactor/dynamic-prope…
…rties Refactoring after new handling of dynamic properties on Entity
- Loading branch information
Showing
2 changed files
with
23 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
<?php | ||
|
||
namespace Longman\TelegramBot\Exception; | ||
|
||
class UndefinedPropertyException extends \LogicException | ||
{ | ||
|
||
} |
@TiiFuchs I'm just testing this and wondering if it makes sense to throw here or just return
null
.Internally for the
getProperty()
call we can just catch and ignore it, but I do wonder how backwards breaking this is for situations where users might try to get a property and expectnull
, which now breaks.