Add Id property to all elements and actions

[dclaux]

Implementation status

• TypeScript (Add ability for renderers to toggle the visibility of rendered elements #494)
• UWP
• WPF
• iOS
• Android
• Documentation

Problem

• Some hosts, especially those that support Action.Http, might need an easy way to correlate an action from the client to its counterpart on the server. Such hosts will likely use an Id property on actions (added after the card is received) anyway, so we might as well make it official
• Still in the context of Action.Http, where the response to a POST call might contain instructions for the host replace all or a portion of a card with new content, having an Id property available on elements would make it easy to remove an element from a card's element tree and insert a new one.

Solution

Add the following property on all element and action types

Property	Type	Description
Id	string	Uniquely identifies the element or action within a card. If duplicate Ids are used in a given card, the first occurrence "wins."

[matthidinger]

The concept sounds good to me. So this would not be a required property then?

[dclaux]

It will be at the discretion of hosts. Some hosts might want to make the Id property of an action required, some might not. I don't think the Id property of an element would be required at all.

[tomlm]

works for me too.

[matthidinger]

@riarenas did we already add this to UWP by chance?

[riarenas]

This is done in UWP for Actions and CardElements. Should this apply to elements that only exist inside specific containers such as choices, facts and columns?

[riarenas]

According to the current schema documentation, column should have an id, but choice and fact should not. Shared model and UWP renderer all reflect that.

[matthidinger]

That's how it is in C# as well, since Fact and Choice are not "typed" elements which is where we added the Id property.

[dclaux]

This seems to be done across the board, closing.

[andrewleader]

Looks like this never was documented, re-opening till that's complete

[RebeccaAnne]

This is documented in main and will go out with the next website deployment.