Java: ChatMessageContent should provide setters for all properties

Open
#144 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, mongodb
Domain
backend, databases

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.

Description

java

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.

Dominant language
Java
Stars
276
Forks
56
Avg merge
17h 45m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/semantic-kernel-java

All issues in microsoft/semantic-kernel-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.