rfc:json_throw_on_error
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:json_throw_on_error [2017/09/10 01:27] – clarify reasoning ajf | rfc:json_throw_on_error [2017/09/24 15:02] – <php>JSON_THROW_ON_ERROR</php> ajf | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PHP RFC: JSON_THROW_ON_ERROR ====== | ====== PHP RFC: JSON_THROW_ON_ERROR ====== | ||
- | * Version: 1.0 | + | * Version: 1.0.2 |
* Date: 2017-09-10 | * Date: 2017-09-10 | ||
* Author: Andrea Faulds | * Author: Andrea Faulds | ||
Line 12: | Line 12: | ||
===== Proposal ===== | ===== Proposal ===== | ||
- | This RFC instead proposes adding a new option flag value for < | + | This RFC instead proposes adding a new option flag value for < |
< | < | ||
- | At the present time, there would be no change to the default error behaviour. It would be worthwhile considering whether to eventually deprecate not using < | + | Note that when given an invalid depth parameter, < |
+ | |||
+ | At the present time, there would be no change to the default error behaviour. It would be worthwhile considering whether to eventually | ||
===== Backward Incompatible Changes ===== | ===== Backward Incompatible Changes ===== | ||
Line 63: | Line 65: | ||
===== Rejected Features ===== | ===== Rejected Features ===== | ||
Keep this updated with features that were discussed on the mail lists. | Keep this updated with features that were discussed on the mail lists. | ||
+ | |||
+ | ===== Changelog ===== | ||
+ | |||
+ | * 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 - initial version |
rfc/json_throw_on_error.txt · Last modified: 2017/10/22 18:44 by ajf