codeconsole commented on PR #16275:
URL: https://github.com/apache/grails-core/pull/16275#issuecomment-5848775772
@matrei thanks. All three are addressed at 714a8973ef.
1. **Date binding moved to #16411.**
- 714a8973ef reverts it here. The commits are on #16411 as 3c504b4607,
5ef4b03bc1 and ac4d02b123.
- #16411 makes the converters render a `Date` through a Julian-aware
formatter again, as the views and Jackson do, so the pre-1582 round trip holds
there. 373d411fc8 renders 1500 and year-44 dates with `as JSON` and binds them
back unchanged.
- 1faa2eead3 scopes the upgrade note to request binding and ISO 8601 with
a `T`. It says the RFC 3339 space form needs its own format and that GraphQL's
date scalars are unchanged.
- #16411's title and description now name the binding change, so it gets
its own changelog entry.
- Here, the date limitation is back in the guide, corrected to what
binding does today: a time with an offset or `Z` is read correctly only with
milliseconds.
2. 5e2296fe1b: the `getExcludes` Javadoc says nothing is excluded where no
application is found.
3. 49931ac992: the recorder registers a request destruction callback that
drops the record as the request completes. A build that fails before the Grails
contribution now leaves nothing on a pooled thread. The test fails a build
part-way, then checks that a later contribution on the same thread doesn't take
the stale record.
Both PRs add an upgrade section 75, so whichever merges second renumbers.
Once both are in, the OpenAPI date limitation can go.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
