Skip to content
This repository has been archived by the owner on Apr 16, 2023. It is now read-only.

[🚀] Persistent information about channels #56

Open
MarkL4YG opened this issue Jun 18, 2019 · 0 comments
Open

[🚀] Persistent information about channels #56

MarkL4YG opened this issue Jun 18, 2019 · 0 comments
Labels
api Related to API changes / additions (internal API) enhancement New feature or request feedback wanted Extra discussion is needed

Comments

@MarkL4YG
Copy link
Member

Describe the solution you'd like
Plugins should be provided a way to persistently store information about a channel just like user profiles allow storing information about that user.

Describe why you would like to see this implemented
When working with channels - especially when creating own channels - often times it is necessary to identify channels later on or store some additional - possibly useful - information about the channel somewhere where it won't just disappear once the framework is restarted.
Since plugins would currently have to implement this feature on their own, an implementation is wanted in the framework.

Additional information
Since channels cannot share profiles like clients do, their profile could be extended by the IChannel interface but that needs closer inspection and some testing.
Invalidation of this information should only be handled in the framework for channels that got deleted (based on event and a start-up check).

@MarkL4YG MarkL4YG added enhancement New feature or request api Related to API changes / additions (internal API) feedback wanted Extra discussion is needed labels Jun 18, 2019
@MarkL4YG MarkL4YG added this to the Stable Release 1.1.0 milestone Jun 18, 2019
@MarkL4YG MarkL4YG removed this from the Stable Release 1.1.0 milestone Jul 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api Related to API changes / additions (internal API) enhancement New feature or request feedback wanted Extra discussion is needed
Development

No branches or pull requests

1 participant