Add support for material-icons

[pocharlebois]

• Based on the npm https://github.com/marella/material-icons
• All material icons as of 1.10.4 in an enum - ie: pie_chart ->
  PieChart("pie_chart") in MDCIconOpts.MDCIconType
• Numbers written out using Proper Case 1MP -> OneMp
• Output is a Span with the right class (Filled, Outlined, TwoTone, etc)
• As elsewhere in KMDC, styling has to be applied externally

Closes #33

[mpetuska]

Great work. Left some minor comments for you to address.

[mpetuska]

Almost there :)

[mpetuska]

As a side note, it would be good if you could stop force-pushing as it often messes up github links, even for linear history. Not a deal-breaker otherwise.

[mpetuska]

Oof, missed it first time around, but since we're wrapping a single html element, it's always a good practice to expose attrs and content builder functions. Have a look at MDCButton for an example how it's done ;)

[rocketraman]

As a side note, it would be good if you could stop force-pushing as it often messes up github links, even for linear history. Not a deal-breaker otherwise.

Sorry @mpetuska our internal workflow for branches is to force push them to keep the history clean. Would you prefer "fixup!" and "squash!" commits during the review process with a final rebase before merge, or do you prefer branches keep a simple linear history, mistakes and all?

[mpetuska]

Well I'm squashing all commits when merging pr anyways to keep pr to commit ratio consistent on master. Not force-pushing to pr branches would make gh permalinks less flakey. But as I said before, this is not a deal breaker, but just my preference.

[mpetuska]

@pocharlebois looks like you pushed a change I requested, but then overridden it with force-push (exactly why I'm not a fan of force-pushing anywhere :D). I've looked at the first push and it is forwarding attrs fine. One more thing that came to mind is new opt

enum class MDCIconBase{Span, I}
//=======
var base: MDCIconBase = MDCIconBase.Span

This would allow people to change base element since mdc-icons supports both, <span> and <i>

[mpetuska]

But I'm happy to ignore base opt as this stage as it can be enhanced later. I'll leave it up to you to decide when you want to merge this.

[rocketraman]

But I'm happy to ignore base opt as this stage as it can be enhanced later. I'll leave it up to you to decide when you want to merge this.

I suspect @pocharlebois would rather merge this as-is, and leave the base opt for later enhancement.