-
Notifications
You must be signed in to change notification settings - Fork 66
Component to create: overlay #28
Comments
I will take this one on. |
SPEC This one should be simple and I guess it is intended to be incorporated with other components (e.g. dialog) main component directive: examples: |
IMHO I think this would make more sense:
No need to include the name overlay in the attribute name as it's not going to be a directive. Also, one of the modes would be the default if omitted. |
I think that makes sense as well. I've submitted a pull request to review. |
Since you're looking at an enum, the next merge of PR's to To be clear, theses aren't guidelines today, but we will be creating issues & assigning to the original directive authors in the coming days on stuff to address. So... when I review all the PRs in the next few days, if you don't have this no worries... we'll just create an issue and assign it to you, but if you want to be proactive, mentioning it now. |
Thanks. I'll review and update accordingly. |
👍 on the spec @andrewconnell suggested |
I've submitted the PR to follow the guideline for attribute validation and error messages. I took a slightly different approach to injecting the logService. Not sure if one method is better then another. @andrewconnell can you change the label of this issue to work in progress? |
Ready for review PR #103 |
Official link to component description & demo: http://dev.office.com/fabric/components/overlay
Screenshot of web analytics for the original http://officeuifabric.com site by @andrewconnell. Use this to see what are the most popular components: http://imgur.com/gallery/buUcyQv
The text was updated successfully, but these errors were encountered: