Skip to content

try_get_anything - converts a 32 hex string to UUID #487

Closed

Description

The library is modifying the content of payload just because the content has something that can taken by UUID class.

This is failing the schema validation down the road.

The location of the culprit

Activity

  1. moved this to Needs Triage 🔍 in Kiotaon Jul 21, 2025
  2. ksachdeva commented on Aug 18, 2025

    @ksachdeva
    Author

    Hi,

    Any update or guidance on this?

    This conversion to a string just because it is a 32 hex string to UUID is invalid and caused the schema validation issues later in my app.

    Regards
    Kapil

  3. mmarseu commented on Apr 30, 2026

    @mmarseu

    I'd like to +1 this issue. I've just stumbled over the same problem.
    To generalize, try_get_anything is IMO too aggressive in it's type guessing/coercion. Just because a string looks remotely like a specific type doesn't mean that the user wants it to be that type.

    As a rule, the developer should be able to control deserialization but I can't find any way to do that.

    For additional context: I'm indirectly using this package through microsoftgraph/msgraph-sdk-python and ran into the issue when fetching SharePoint list items with fields that contain 32 character hash values.

  4. added a commit that references this issue on Jul 18, 2026
    08ecf9f
  5. moved this from Needs Triage 🔍 to Done ✔️ in Kiotaon Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    • Status
      Done ✔️

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions