Flask-discord-interactions

Latest version: v2.1.2

Safety actively analyzes 682471 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 7

1.0.3

Discord, as of now, has moved the `resolved` field out of the base `interaction` object and into the `interaction.data` object. This release accommodates this change. Thank you to TheDevFreak for reporting this issue.

Please upgrade to this release if you are experiencing issues with using the Member, Role, etc. types.

1.0.2

Previously, each instance of AsyncContext created its own aiohttp ClientSession to send requests to Discord. However, it was unclear when to close this session, as background tasks could continue to make use of it after the initial response had been sent.

This release uses a ClientSession stored at the application level instead. This session is created using `app.before_serving` and closed using `app.after_serving` automatically for Quart apps. This is handled within `app.set_route_async`.

This release deprecates `AsyncContext.close()`.

1.0.1

Hotfix for issue 43.

1.0.0

This PR adds several new features:
* Additional option types `NUMBER` and `MENTIONABLE` (38, thank you williamhatcher!)
* Command permissions (21, 40)
* The SelectMenu component (37, 39)

This is version 1.0.0. This means that this library is committing to maintaining a stable API going forward, in order to support the numerous projects that have begun using it.

> **How do I know when to release 1.0.0?**
> If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.
> \- [SemVer FAQ](https://semver.org/spec/v2.0.0.html#how-do-i-know-when-to-release-100)

0.1.12

This release fixes an issue with the construction of Context objects (29, 30). Thank you to jethrob for reporting this issue!

Other changes:
* Fixed issue with subcommand return value handling (1869ceb9)
* Decreased minimum Python version to 3.7, we were already running unit tests targeting it (219efd75)

0.1.11

This PR adds support for:

* Message Components (25)
* Storing state in custom IDs (27)

It also fixes some permissions-related bugs (acbe032) and uses the new API endpoint for updating commands (24).

Page 5 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.