Hikari-lightbulb

Latest version: v2.3.5

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

Scan your dependencies

Page 1 of 3

3.0.0a0

> [!WARNING]
> This is an **ALPHA** release of hikari-lightbulb version 3. As such it is unfinished and you should probably be using the most recent release of version 2 instead.

This version is a complete rewrite of the entire library from scratch. The API reference documentation can be found [here](https://hikari-lightbulb.readthedocs.io/en/v3/) however the guides **have not** been updated. If you for some reason wish to use this version and have questions you should ask in the V3 thread of the lightbulb channel in the [hikari discord](https://discord.gg/hikari) - or you can open a discussion on the repository.

2.3.5

What's Changed
- Fix incorrect parameters being passed to _get_bucket which prevented the add_cooldown decorator from functioning correctly.

2.3.4

What's Changed

- Add validators to options in PrefixContext

- Fix custom option converter not being initialized for slash commands.

- Implemented slotting in some classes.

- Fixed localization options not being passed to subcommands or command options.

- Added case insensitive prefixes.

- Add support for Python 3.12.

- Bump hikari requirement to 2.0.0.dev122.

2.3.3

- `bucket` attribute has been added to `lightbulb.errors.MaxConcurrencyLimitReached`.

- Fix button navigator due to hikari breaking changes.

- Autocomplete callbacks may no longer return instances of `hikari.CommandChoice` as it has been deprecated. Use `AutocompleteChoiceBuilder` instead.

2.3.2

**Potentially Breaking Changes**

- Module `lightbulb.utils.parser` has been moved up a level to `lightbulb.parser`.

- `OptionsProxy` will now raise an `AttributeError` when trying to access an option that does not exist.

**Other Changes**

- Slash commands now have full custom converter support.

- Permission checks improved to use interaction permission fields where appropriate.

- Fix `lightbulb.commands.base.ApplicationCommand.nsfw` not applying correctly for global commands.

- Implement `min_length` and `max_length` for command options.

- Fix deferral of slash subcommands not working as intended.

2.3.1

**Potentially Breaking Changes**

- `lightbulb.cooldown_algorithms.CooldownStatus` has been moved from the `buckets` module to the
`cooldown_algorithms` module.

- `commands_run` attribute has been removed from the `lightbulb.buckets.Bucket` class.

**Other Changes**

- Add `lightbulb.commands.base.CommandLike.nsfw` and `nsfw` kwarg in `lightbulb.decorators.command`
decorator in order to mark a command as only usable in NSFW channels.

- Deprecate `lightbulb.checks.nsfw_channel_only`. Use the above new feature instead. The check will
be removed in version `2.4.0`.

- Add `lightbulb.context.base.Context.respond_with_modal`. Note that this will not work if called
on an instance of `lightbulb.context.prefix.PrefixContext`.

- Add `lightbulb.plugins.Plugin.listeners`.

- Improve `lightbulb.converters.special.MessageConverter` to support conversion of `channelid-messageid` format.

- Implement multiple built-in cooldown algorithms which can be specified when adding a cooldown to a command.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.