You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to risks of regression, let's add a StreamReadFeature for determining whether JsonParser.close() should clear current token information, accessible via JsonParser.currentToken().
If enabled (default for 2.20), current token IS cleared (set to null); if disabled, it remains as it was at time of close().
Default planned to be true (clear current token) as that seems more intuitive choice; but note that existing (2.19) behavior what false will do.
Since this is for 2.20, we have still time to consider choice of default.
(for 3.0 it should probably be true, at any rate).
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
(follow-up to #1438 )
Due to risks of regression, let's add a
StreamReadFeature
for determining whetherJsonParser.close()
should clear current token information, accessible viaJsonParser.currentToken()
.If enabled (default for 2.20), current token IS cleared (set to
null
); if disabled, it remains as it was at time ofclose()
.Default planned to be
true
(clear current token) as that seems more intuitive choice; but note that existing (2.19) behavior whatfalse
will do.Since this is for 2.20, we have still time to consider choice of default.
(for 3.0 it should probably be
true
, at any rate).The text was updated successfully, but these errors were encountered: