Closed (fixed)
Project:
JSON:API Extras
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
15 Mar 2018 at 11:03 UTC
Updated:
3 Oct 2019 at 15:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
vtcore commentedPatch suggestion.
Comment #3
e0ipsoComment #4
e0ipsoThanks for the patch. Kicking off tests.
Comment #5
vtcore commentedTests seem to pass. Can you commit to the 1.x branch?
Comment #7
e0ipsoFixed for 1.x (unsupported), now opening for 2.x.
Comment #9
e0ipso:-( I had to revert this commit because this is breaking the JSON Schema for these fields, while trying to port it to 2.x.
Take a look at
getJsonSchemainDateTimeEnhancerBase.Comment #10
ndobromirov commentedHi here is an attempt to have the schema correct with the string / array of strings variation.
Comment #11
ndobromirov commentedHere is another iteration of the patch that now I was able to test and schema validation passes on date range fields.
Comment #13
e0ipsoThanks for this contribution! Sorry it took so long to get it merged.
Comment #15
andsigno82 commentedHi, have to reopen this. using the 3.x-dev version.
the enhancer still return this error when you select either datetime or timestamp
AH01071: Got error 'PHP message: TypeError: DateTime::__construct() expects parameter 1 to be string, array given in /contenta/web/core/lib/Drupal/Component/Datetime/DateTimePlus.php