Replies: 1 comment
-
Would really appreciate a 👍🏻 or 👎🏻 if this is an approach worth considering. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In order to create new message types, the following files have to be modified:
This means forking the project and making changes that almost negate the ability to use the package unless you are 100% OK with the existing message types.
By making the message type relatable to a plugin system, we could make extending the message system a lot simpler while allowing the core to improve without having to fork it. Our internal chat system currently does this and it works well. The solution might look something like this:
const
into a repository.These changes would make creation of new types of messages as easy as:
Example
and then in a provider somewhere:
While the initial work would be somewhat involved, I think the long term benefits would be huge.
Beta Was this translation helpful? Give feedback.
All reactions