microsoft / microsoft/AdaptiveCards
[Designer] Capitalization of property values inconsistent
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Setting property values with ELEMENT PROPERTIES will (usually?) capitalize the value. For some properties in certain contexts, the capitalized value is marked with a warning in the CARD PAYLOAD EDITOR.
I've not been able to establish consistent circumstances but a simple example is below.
New Card => Flight Itinerary
Microsoft Teams - Light
v1.2
Changing the value in the EDITOR to lowercase satisfies the warning temporarily but it will revert at some point after making changes.
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 in the CARD PAYLOAD EDITOR and reproduce the New Card => Flight Itinerary example using ELEMENT PROPERTIES. Compare the capitalization, warning, and value reversion after edits; done means property values remain consistent and do not trigger an incorrect warning.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100