Skip to content

Conversation

sofc-T
Copy link

@sofc-T sofc-T commented Sep 30, 2025

What kind of change does this PR introduce?

#1048 issue fix

using pydantic parsing for safer extraction - as suggested on a previous closed PR

defined a new class ApiErrorModelfor pydantic parsing

Bug fix, feature, docs update, ...

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.
#1048

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@sofc-T sofc-T changed the title Issue 1048 fix fix: Issue 1048 fix - pydantic parsing Sep 30, 2025
@o-santi
Copy link
Contributor

o-santi commented Oct 1, 2025

I took a closer look at the error reported in #1048 and it isn't valid. The error has nothing to do with parsing, and it does not make sense that it happens as resp is defined on the line above of the error. I can only assume it is due to AI hallucination, so I'll be closing this.

I still intend to do pydantic parsing of the errors in the future, but it should be more well planned.

@o-santi o-santi closed this Oct 1, 2025
@sofc-T
Copy link
Author

sofc-T commented Oct 1, 2025 via email

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.

2 participants