microsoft / microsoft/AdaptiveCards
[Designer] Designer and schema don’t agree on casing of attribute values
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Problem Description
Designer creates certain attributes with an upper-cased first letter, which then shows up in code view as not adhering to the JSON schema:
When the casing is corrected to match the schema, designer then no longer recognizes it:
Affected properties that I have seen so far: size, weight, color, horizontalAlignment, spacing. There might be others.
Card JSON
{
"type": "AdaptiveCard",
"body": [
{
"type": "TextBlock",
"size": "Medium",
"weight": "Bolder",
"text": "${title}",
"style": "heading",
"wrap": true
}
],
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.6"
}
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
Reproduce the mismatch using the Card JSON in the issue, checking the Designer and the JSON schema for size, weight, color, horizontalAlignment, and spacing. Compare the casing accepted by each view, then verify that the affected properties use consistent casing and remain recognized by both the Designer and schema validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100