8000 PART-548 | Give RICH_TEXT a distinct enum value so STRING and RICH_TEXT are not aliases by Aryamanz29 · Pull Request #857 · atlanhq/atlan-python · GitHub
[go: up one dir, main page]

Skip to content

PART-548 | Give RICH_TEXT a distinct enum value so STRING and RICH_TEXT are not aliases#857

Open
Aryamanz29 wants to merge 3 commits intomainfrom
PART-548
Open

PART-548 | Give RICH_TEXT a distinct enum value so STRING and RICH_TEXT are not aliases#857
Aryamanz29 wants to merge 3 commits intomainfrom
PART-548

Conversation

@Aryamanz29
Copy link
Member

No description provided.

… not aliases

STRING and RICH_TEXT shared the same enum value ("string"), making them
indistinguishable in Python's Enum. This caused STRING attributes to
incorrectly get is_rich_text=True and RICH_TEXT multi-value restrictions
to apply to STRING.

Fixes PART-548

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Aryamanz29 Aryamanz29 self-assigned this Mar 13, 2026
@Aryamanz29 Aryamanz29 added the bugfix Bug fix pull request label Mar 13, 2026
Copy link
@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The test file imported pyatlan_v9, which transitively pulled all of
pyatlan_v9 into mypy's scope when checking `pyatlan tests`.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Bug fix pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0