Dispatch Events #33
Merged
Dispatch Events #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds three events that will be dispatched:
SettingsFlushed
Event is dispatched when the
flushmethod is called on the settings service. The event receives the following arguments:$keys: The subset of keys being flushed, if any$teamId: The current team id set on the settings service$context: The current context object set on the settings serviceSettingWasDeleted
Event is dispatched when a setting is deleted. The event receives the following arguments:
$key: The key of the setting being deleted$storageKey: The generated key used by the storage mechanism on the driver$cacheKey: The generated cache key of the setting$teamId: The current team id set on the settings service$context: The current context object set on the settings serviceSettingWasStored
Event is dispatched when a setting is deleted. The event receives the following arguments:
$key: The key of the setting being stored$storageKey: The generated key used by the storage mechanism on the driver$cacheKey: The generated cache key of the setting$value: The value being set for the setting$teamId: The current team id set on the settings service$context: The current context object set on the settings serviceNote: When caching is enabled, the event will only fire if the value has changed for an already persisted setting.