Skip to content

ECOM-64901 - add orderBy field's support to variations for GET requests only - #567

Merged
ivshinrl-ls merged 1 commit into
masterfrom
ECOM-64901
Nov 4, 2026
Merged

ivshinrl-ls merged 1 commit into
masterfrom
ECOM-64901

Conversation

@ivshinrl-ls

Copy link
Copy Markdown
Contributor

subj

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The change adds nullable, response-only orderBy support for fetched variations and includes contract and Gson coverage for populated, missing, and explicit null values.

No open issues 🎉

What changed in this PR

Adds support for deserializing the optional orderBy field on fetched product variations while keeping it nullable and read-only for update requests.

Changes:

  • Adds nullable orderBy to FetchedVariation.
  • Updates nullable-property and non-updatable DTO contract rules.
  • Adds Gson tests for populated, missing, and explicit null values.
File Description
src/​test/​kotlin/​com/​ecwid/​apiclient/​v3/​rule/​nullablepropertyrules/​FetchedVariationRules.kt Allows nullable orderBy values in fetched variations.
src/​test/​kotlin/​com/​ecwid/​apiclient/​v3/​rule/​NonUpdatablePropertyRules.kt Marks orderBy as read-only for variation updates.
src/​test/​kotlin/​com/​ecwid/​apiclient/​v3/​jsontransformer/​gson/​GsonTransformerTest.kt Verifies orderBy deserialization for present, missing, and null values.
src/​main/​kotlin/​com/​ecwid/​apiclient/​v3/​dto/​variation/​result/​FetchedVariation.kt Adds the optional response-only orderBy property.

Review effort: Lite

@ivshinrl-ls
ivshinrl-ls merged commit d9b19a7 into master Nov 4, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants