rfc:json_throw_on_error

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
rfc:json_throw_on_error [2017/09/24 14:47] – v1.0.2 ajfrfc:json_throw_on_error [2017/09/25 21:21] – vote ajf
Line 3: Line 3:
   * Date: 2017-09-10   * Date: 2017-09-10
   * Author: Andrea Faulds   * Author: Andrea Faulds
-  * Status: Under Discussion+  * Status: In Voting
   * First Published at: http://wiki.php.net/rfc/json_throw_on_error   * First Published at: http://wiki.php.net/rfc/json_throw_on_error
  
Line 16: Line 16:
 <php>JsonException</php> would be a new class that subclasses <php>Exception</php>. <php>JsonException</php> would be a new class that subclasses <php>Exception</php>.
  
-At the present time, there would be no change to the default error behaviour. It would be worthwhile considering whether to eventually slowly deprecate not using <php>JSON_THROW_ON_ERROR</php> and then change the default behaviour, however.+Note that when given an invalid depth parameter, <php>json_decode()</php> outputs a warning and returns NULL. This behaviour is unaffected by <php>JSON_THROW_ON_ERROR</php> because it does not affect the global error state at present, has no corresponding error code to throw an exception with, and is not dependent on user input. Similarly, parameter parsing errors continue to produce warnings (when not in strict mode) because their error behaviour cannot be conditioned on the value of a parameter being parsed. Both can be caught by a user error handler that converts errors to exceptions. 
 + 
 +At the present time, there would be no change to the default error behaviour. It would be worthwhile considering whether to eventually slowly deprecate not using <php>JSON_THROW_ON_ERROR</php> and then change the default behaviour, but this RFC does not do this.
  
 ===== Backward Incompatible Changes ===== ===== Backward Incompatible Changes =====
Line 40: Line 42:
 As mentioned earlier, it may be desirable to deprecate the default behaviour eventually. As mentioned earlier, it may be desirable to deprecate the default behaviour eventually.
  
-===== Proposed Voting Choices ===== +===== Vote ===== 
-This is not a language change, merely a small addition to the JSON extension, so it only technically requires a 50%+1 majority.+This is not a language change, merely a small addition to the JSON extension, so it only technically requires a 50%+1 majority. However, it's a 2/3 vote. It is a simple Yes/No vote on whether to accept this RFC and merge the patch. 
 + 
 +Voting started 2017-09-25 and ends 2017-10-05.
  
-It would be a simple Yes/No vote on whether to accept this RFC and merge the patch.+<doodle title="Accept and merge JSON_THROW_ON_ERROR for PHP 7.3?" auth="ajf" voteType="single" closed="false"> 
 +   * Yes 
 +   * No 
 +</doodle>
  
 ===== Patches and Tests ===== ===== Patches and Tests =====
Line 66: Line 73:
 ===== Changelog ===== ===== Changelog =====
  
-  * v1.0.2 - change behaviour to leave global error flag untouched, rather than clearing it+  * v1.0.2 - change behaviour to leave global error flag untouched, rather than clearing it; note depth, param-parsing errors
   * v1.0.1 - cover details of the patch not previously mentioned   * v1.0.1 - cover details of the patch not previously mentioned
   * v1.0 - initial version   * v1.0 - initial version
rfc/json_throw_on_error.txt · Last modified: 2017/10/22 18:44 by ajf

Page Tools