Open codepretty opened 6 years ago
the simplest solution we might consider is to make this temporary
prop being Teams-specific - so that it will be introduced for Teams only, and not as something that is general enough to be part of Stardust (and, actually, we might reason about atMention
and timestamp
ones in the same way).
Please, let me know what do you think about this being a solution from a conceptual point of view (as currently there is no way to make props theme-specific, but let's pretend for a second that it exists) - would it make the problem easier to solve? To me it seems that we will be able to solve quite a lot of naming concerns much easier if we will be able to split 'general web' domain from 'Teams-specific' one for certain props.
This RFC was raised in regard to a new Text prop, see #151.
Problem
I have found cases of text usage that indicate a non-permanent state. In some cases, it appears as a temporary or hoisted state. In other cases, it appears to indicate a preview state.
Open question: Does anyone know of examples of this where the text isn't italic?
Application usages
Microsoft Teams
VS Code
Others??
Proposals
Goal
Determine what is the right name to use for this type of text
Some options