fix: added description to paging field to not overwite python import#27673
fix: added description to paging field to not overwite python import#27673
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the JSON Schema for EntityHistory to add a description annotation to the paging property so downstream code generation (notably Python/Pydantic models) emits a Field(..., description=...) rather than a plain = None default.
Changes:
- Added
description: "Pagination information"toproperties.paginginentityHistory.json. - Adjusted the paging
$refstring to./paging.json(functionally equivalent relative reference).
✅ TypeScript Types Auto-UpdatedThe generated TypeScript types have been automatically updated based on JSON schema changes in this PR. |
Code Review ✅ ApprovedAdded a docstring description to the paging field to prevent Python import conflicts. No issues found. OptionsDisplay: compact → Showing less information. Comment with these commands to change:
Was this helpful? React with 👍 / 👎 | Gitar |
|
🔴 Playwright Results — 3 failure(s), 17 flaky✅ 3945 passed · ❌ 3 failed · 🟡 17 flaky · ⏭️ 86 skipped
Genuine Failures (failed on all attempts)❌
|
…pen-metadata#27673) * fix: added description to paging field to not overwite python import * Update generated TypeScript types --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>



Describe your changes:
Fixes build break from https://github.com/open-metadata/OpenMetadata/pull/26307/changes#diff-d2552f934decdcbb8b829ca968c08390994c620f419a1fdd580f6f175b64c4d0R114-R115 paging added to entityHistory.
Added description so model generated in python will be
and not
Type of change:
Checklist:
Fixes <issue-number>: <short explanation>