# Remove Callbacks in Beacon

In the `@beacon.li/bar` package, you can remove previously added callbacks to customize the behavior of BeaconBar further. This allows you to manage your callbacks dynamically and maintain the desired functionality.

#### Removing a Callback

To remove a callback, you can use the `Beacon.removeCallback` method. This method takes one parameter:

* `key` (string): The key of the callback you want to remove.

Here's how to use it:

```
import { Beacon } from '@beacon.li/bar';
Beacon.removeCallback('your_callback_key');
```

In the example above, we've removed the callback with the key `'your_callback_key'`. This will unregister the callback associated with that key.

#### Benefits of Removing Callbacks

Removing callbacks can be beneficial in scenarios where:

* You no longer need a specific callback for a particular event.
* You want to replace a callback with a new one to update the behavior.
* You want to streamline your code and remove unused or outdated callbacks.

#### Key Consideration

When removing callbacks, ensure that you use the exact key associated with the callback you want to remove. Removing a callback with an incorrect or non-existent key will have no effect.

By following these steps, you can effectively manage and remove callbacks to maintain the desired functionality of BeaconBar in your application.
