microsoft / microsoft/semantic-kernel-java
Java: ChatMessageContent should provide setters for all properties
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 276
- Forks
- 56
- Avg merge
- 17h 45m
- Merged PRs (30d)
- 4
Description
For scenarios like integrating with MongoDB, you need to be able to have zero-parameter constructors with setters on all of the properties. Because there are not setters for authorRole, contents, or encoding, ChatMessageContent cannot be deserialized from MongoDB.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Java ChatMessageContent class and reviewing its existing properties, constructors, and serialization-related tests or usages. Confirm how MongoDB deserialization is expected to instantiate it, then verify that all named properties can be assigned and that the relevant tests cover zero-parameter construction and deserialization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mongodb
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100