Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System message information should not be tied to content #102

Closed
rikashore opened this issue Oct 19, 2021 · 0 comments
Closed

System message information should not be tied to content #102

rikashore opened this issue Oct 19, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@rikashore
Copy link

As of right now, when fetching a message, the content field can either be a string or a JSON object. This behaviour makes deserialization of a message's content in strongly typed languages such as C# an issue. Looking at this, it doesn't make sense for information about a system message being tied to it's content. I suggest having a separate field that contains this info.

@insertish insertish added the enhancement New feature or request label Oct 26, 2021
@insertish insertish added this to Needs Triage in Release Tracker via automation Oct 26, 2021
@insertish insertish moved this from Needs Triage to Version Tasks in Release Tracker Oct 26, 2021
@insertish insertish added this to the 0.5.3: Backend Overhaul milestone Oct 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Release Tracker
Version Tasks
Development

No branches or pull requests

2 participants