fix: Resolve Python keyword conflict in Pydantic models

- Renamed 'IN' attribute in TokenPatternString and TokenPatternNumber models
  to 'IS_IN' to avoid conflict with Python's 'in' keyword.
- Updated the corresponding Field alias to 'is_in' from 'in'.
- This fix prevents a TypeError upon the initialization of these models due
  to the improper use of a reserved Python keyword as an attribute.
This commit is contained in:
teleprint-me 2023-07-12 18:13:54 -04:00
parent ddffd09602
commit bb7a13e777
No known key found for this signature in database
GPG Key ID: B0D11345E65C4D48

View File

@ -179,7 +179,7 @@ def validate_token_pattern(obj: list) -> List[str]:
class TokenPatternString(BaseModel):
REGEX: Optional[Union[StrictStr, "TokenPatternString"]] = Field(None, alias="regex")
IN: Optional[List[StrictStr]] = Field(None, alias="in")
IS_IN: Optional[List[StrictStr]] = Field(None, alias="is_in")
NOT_IN: Optional[List[StrictStr]] = Field(None, alias="not_in")
IS_SUBSET: Optional[List[StrictStr]] = Field(None, alias="is_subset")
IS_SUPERSET: Optional[List[StrictStr]] = Field(None, alias="is_superset")
@ -226,7 +226,7 @@ class TokenPatternString(BaseModel):
class TokenPatternNumber(BaseModel):
REGEX: Optional[StrictStr] = Field(None, alias="regex")
IN: Optional[List[StrictInt]] = Field(None, alias="in")
IS_IN: Optional[List[StrictInt]] = Field(None, alias="is_in")
NOT_IN: Optional[List[StrictInt]] = Field(None, alias="not_in")
IS_SUBSET: Optional[List[StrictInt]] = Field(None, alias="is_subset")
IS_SUPERSET: Optional[List[StrictInt]] = Field(None, alias="is_superset")