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
Requesting a resource with a link like /my-resource?forDate=2017-10-11T00:00:00.000Z&filter[id]=123,124 gives a Date object for the forDate param. Currently the create-query-string function has no knowledge of correctly serializing a date which results in a page link like: /my-resource?&filter[id]=123,124 which is invalid.
Any ideas are welcome @zacharygolba . I can make a PR if you approve of the solution. I'm still a bit in doubt whether or not to make the assumption of an ISO8601 date.
Would need a "back" port to master as well, as I see the implementation has changed.
nickschot
changed the title
[bug] (page) links not serialized properly when one of the params is a date
(page) links not serialized properly when one of the params is a date
Oct 24, 2017
Requesting a resource with a link like
/my-resource?forDate=2017-10-11T00:00:00.000Z&filter[id]=123,124
gives a Date object for the forDate param. Currently the create-query-string function has no knowledge of correctly serializing a date which results in a page link like:/my-resource?&filter[id]=123,124
which is invalid.Can be solved by modifying
create-page-links
to:This does expect the user to use ISO8601 dates.
The text was updated successfully, but these errors were encountered: