-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Refactor Format class #3563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Refactor Format class #3563
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e9afd76
Refactor Format class
paulbalandan 584ee4d
Add and modify tests
paulbalandan 9b06244
Fix phpstan related errors
paulbalandan 44f24ba
Add deprecation notice to changelog
paulbalandan d03aa81
Return accidentally deleted code in test
paulbalandan 2fb987f
Add @throws block
paulbalandan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,22 +1,100 @@ | ||
<?php namespace CodeIgniter\Format\Exceptions; | ||
<?php | ||
|
||
/** | ||
* CodeIgniter | ||
* | ||
* An open source application development framework for PHP | ||
* | ||
* This content is released under the MIT License (MIT) | ||
* | ||
* Copyright (c) 2014-2019 British Columbia Institute of Technology | ||
* Copyright (c) 2019-2020 CodeIgniter Foundation | ||
* | ||
* Permission is hereby granted, free of charge, to any person obtaining a copy | ||
* of this software and associated documentation files (the "Software"), to deal | ||
* in the Software without restriction, including without limitation the rights | ||
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
* copies of the Software, and to permit persons to whom the Software is | ||
* furnished to do so, subject to the following conditions: | ||
* | ||
* The above copyright notice and this permission notice shall be included in | ||
* all copies or substantial portions of the Software. | ||
* | ||
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
* THE SOFTWARE. | ||
* | ||
* @package CodeIgniter | ||
* @author CodeIgniter Dev Team | ||
* @copyright 2019-2020 CodeIgniter Foundation | ||
* @license https://opensource.org/licenses/MIT MIT License | ||
* @link https://codeigniter.com | ||
* @since Version 4.0.0 | ||
* @filesource | ||
*/ | ||
|
||
namespace CodeIgniter\Format\Exceptions; | ||
|
||
use CodeIgniter\Exceptions\ExceptionInterface; | ||
use RuntimeException; | ||
|
||
class FormatException extends \RuntimeException implements ExceptionInterface | ||
/** | ||
* FormatException | ||
*/ | ||
class FormatException extends RuntimeException implements ExceptionInterface | ||
{ | ||
/** | ||
* Thrown when the instantiated class does not exist. | ||
* | ||
* @param string $class | ||
* | ||
* @return FormatException | ||
*/ | ||
public static function forInvalidFormatter(string $class) | ||
{ | ||
return new static(lang('Format.invalidFormatter', [$class])); | ||
} | ||
|
||
/** | ||
* Thrown in JSONFormatter when the json_encode produces | ||
* an error code other than JSON_ERROR_NONE and JSON_ERROR_RECURSION. | ||
* | ||
* @param string $error | ||
* | ||
* @return FormatException | ||
*/ | ||
public static function forInvalidJSON(string $error = null) | ||
{ | ||
return new static(lang('Format.invalidJSON', [$error])); | ||
} | ||
|
||
/** | ||
* This will never be thrown in travis-ci | ||
* Thrown when the supplied MIME type has no | ||
* defined Formatter class. | ||
* | ||
* @param string $mime | ||
* | ||
* @return FormatException | ||
*/ | ||
public static function forInvalidMime(string $mime) | ||
{ | ||
return new static(lang('Format.invalidMime', [$mime])); | ||
} | ||
|
||
/** | ||
* Thrown on XMLFormatter when the `simplexml` extension | ||
* is not installed. | ||
* | ||
* @return FormatException | ||
* | ||
* @codeCoverageIgnore | ||
*/ | ||
public static function forMissingExtension() | ||
{ | ||
return new static(lang('Format.missingExtension')); | ||
} | ||
|
||
} |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're currently all over the place on these. Let's see if @lonnieezell wants to make a call on the styling of namespaces before we change them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with this. Currently it's a mix, and we need a definitive style guide for this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My personal preference has always been on line 1, but it seems my IDE and lots of other programmers prefer it with a blank space after the opening php tag. I'm fine with either of those options. Not of fan of having the CI docblock above it, though. I think namespace should be the first item in the file.
So do either of you have preferences on first line vs third line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been doing it on first line but I think I picked that up from you ;) I don't use an IDE so I'm not sure how much work it is to fight against one. Are there any standards? Does our CS have options that might indicate a "default"?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am following PSR-12.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good with following the PSR on this. I had forgotten 12 got released, actually, so thanks for the reminder.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh that's great! Yes we should definitely move towards that then. The consensus is third line for namespace then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Third line for namespace if no file-level doc block. Namespace after doc block if present. This is following PSR12.
I'll take note on this on my upcoming PR on php-cs-fixer fixes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bummer - namespace after file docblock is in PSR. Oh well. Can't have it all :)