No fix needed - date transformers work correctly with @hey-api/client-fetch #2901
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The reported issue describes date transformers not being generated for inline array object schemas. Investigation confirms this issue exists in
legacy/fetchbut not in@hey-api/client-fetch.Verification
Tested with the OpenAPI spec from the issue containing three scenarios:
With
@hey-api/client-fetch, all three scenarios generate correct transformers:With
legacy/fetch, scenario 3 fails - no transformer is generated despite types beingDate.Recommendation
Users experiencing this issue should migrate from
legacy/fetchto@hey-api/client-fetchplugin, where date transformers work correctly for all schema patterns including inline array objects.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.