Allow menu-trigger to take a menu interface.

[trshafer]

This should enable menus to be more easily extended for custom menu implementations.

Addresses #1560.

[trshafer]

I went back and forth on whether or not to make it an abstract class with many of the implementation details on the abstract class. I went with the interface because it's less invasive to the consumer than an abstract class.

[trshafer]

Force pushed to address the conflict in merge of #1534.

[jelbourn]

It would be good to also have a unit test that binds a dummy impl of MdMenuPanel and assert that a basic action works.

[jelbourn]

If these two are going to be part of this interface, they'll should lose the underscore (which implies "internal api only")

[jelbourn]

Let's call this MdMenuPanel
(generally trying to avoid using the word "interface" in the names of interfaces)

[trshafer]

Hey @jelbourn, I have made the requested updates. Good suggestions. The test really helps demonstrate the creation of custom menus.

[jelbourn]

LGTM aside from a couple last comments. @kara should also take a look

[kara]

LGTM, aside from the one comment. Looks like this needs to be rebased as well

[kara]

Agree with @jelbourn that underscore should be removed if possible

[trshafer]

Hey @kara, thanks for the review. I have removed the underscore from the interface, rebased, squashed my commits, and updated the commit message style.

[kara]

LGTM

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}