Make RFC compliance default
AN
2mo ago+92+92+01234567890123456789-28-28-01234567890123456789
PR checklist
- Read the contribution guidelines.
- Run the following to build the project and update samples:
(For Windows users, please run the script in WSL)./mvnw clean package || exit ./bin/generate-samples.sh ./bin/configs/*.yaml || exit ./bin/utils/export_docs_generators.sh || exit
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./bin/generate-samples.sh bin/configs/java*.
IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed. - If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.
cc Python technical committee: @cbornet @tomplus @krjakbrjak @fa0311
Summary by cubic
Changes the generated Python client to serialize datetime query parameters with RFC 3339 compliant output by default. datetime_format now defaults to None, in which case parameters are formatted with datetime.isoformat() instead of the previous default %Y-%m-%dT%H:%M:%S.%f%z via strftime, so timezone offsets render as -05:00 rather than -0500. Setting datetime_format explicitly still uses that format string.
Migration
- Set
datetimeFormatexplicitly to keep the old default format output. - Tests that assert the old default serialization must be updated to the new RFC 3339 output.