microsoft / microsoft/AdaptiveCards
Convert API properties to optional
Open
Nobody has claimed this yet.
Design Discussion - Needed
Epic
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
As part of the 1.5 feature work many properties have been converted to optional (as breaking changes). This epic tracks considering whether we want to make this more consistent by updating all properties to be exposed as optional and be unset if not included in the json.
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
This issue names no files, tests, or entry points. Start by inventorying the API properties and their JSON deserialization behavior across the repository, then determine the intended optionality and scope for each platform. Done means the behavior is consistent for all properties, with coverage for properties omitted from JSON.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100