Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

field "type" of ChannelOverwriteEntryInfo does not get deserialized properly #1992

Closed
2 tasks done
syncblaze opened this issue Aug 3, 2024 · 0 comments · Fixed by #1993
Closed
2 tasks done

field "type" of ChannelOverwriteEntryInfo does not get deserialized properly #1992

syncblaze opened this issue Aug 3, 2024 · 0 comments · Fixed by #1993
Labels
bug Something isn't working

Comments

@syncblaze
Copy link
Contributor

Steps to reproduce

  1. Get an AuditLogEntry where the action_type is one of these: CHANNEL_OVERWRITE_CREATE | CHANNEL_OVERWRITE_UPDATE | CHANNEL_OVERWRITE_DELETE
  2. audit_log_entry.options.type is of type str instead of PermissionOverwriteType
  3. This is because discord returns this for some reason as a string instead of beeing consistend. Look here
  4. Normal overwrite object uses int as shown here

Expected result

If the bug wasn't there there should be a PermissionOverwriteType object instead of a str in the type field.

Actual result

There is a str.

System info

hikari (2.0.0.dev126) [f65737f4]
located at C:\Users\Server\PycharmProjects\Pyro\venv\Lib\site-packages\hikari
CPython 3.12.4 MSC v.1940 64 bit (AMD64)
Windows DESKTOP-UPP6BLS 11 10.0.22631 AMD64 AMD64 Family 23 Model 96 Stepping 1, AuthenticAMD

Further info

No response

Checklist

  • I have made sure to remove ANY sensitive information (bot token, passwords, credentials, personal details, etc.).
  • I have searched the issue tracker and have made sure it's not a duplicate. If it is a follow up of another issue, I have specified it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant