-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sentiment should be renamed to style #2968
Comments
@paulcam206 / @andrewleader why is this a specbug? I understand this needs to be changed in code yes? Also do we want to create platform-specific workitems? @RebeccaAnne + @nesalang FYI this rename might be coming to you guys respectively |
Maybe Paul assigned the SpecBug label thinking that's how we track bugs that are a result of spec bugs? Idk 😵 We have lots of labels 😛 Yes, this needs to be changed in code. Platform-specific work items sound good to me if that's what you'd like! Up to the dev team :) |
I added As it stands, the spec still calls for |
Awesome! Great find @paulcam206 and thanks a ton @RebeccaAnne for being on top of this including getting the children spun up and assigned! Looks like this should land in 1.2 just fine. |
The spec seems to be correct, it should be an enum. There's simply the option for hosts to extend support and add different values (which UWP added). That's a host-specific feature. From the authoring side, it still should be an enum for ease of authoring (if they're sending to a host that has a custom value, they'll need to do something different... same as if they're sending to a host that has a custom container style) |
fair enough! 👍 |
As part of #2981 I made the JS implementation extensible. |
Per email thread, the action
sentiment
property should be renamed tostyle
.The text was updated successfully, but these errors were encountered: