Deprecate ProgrammingError in favor of LogicException#5511
Open
TheSyscall wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mark
ProgrammingErroras@deprecatedin favor of PHP SPLLogicException.ProgrammingErroris a thin wrapper aroundIcingaExceptionthat carries no additional semantics beyond what PHP's built-inLogicExceptionalready provides.The one behavioral difference is that
IcingaExceptionaccepts a vsprintf-style format string and arguments in its constructor, whichLogicExceptiondoes not.LogicExceptionis the PHP SPL type for errors that represent violations of program logic, incorrect API usage, missing setup, and violated preconditions, which is exactly whatProgrammingErrorwas used for.