Components: Documentation is not in sync with latest build

[zanderle]

Bug, feature request, or proposal:

Feature request or proposal

What is the expected behavior?

I'd expect documentation to either explicitly state that it's showing whatever is on master (and not the latest build). Or even better, show what's on the latest build instead.

What is the current behavior?

Currently, the documentation is on master.

What are the steps to reproduce?

I was working with md-select and was trying to use panelClass which is already in the documentation, but the latest build (2.0.0-beta.6) doesn't have it implemented yet.

What is the use-case or motivation for changing an existing behavior?

It can be quite confusing figuring out why the feature that is documented, doesn't work on the latest build.

[jelbourn]

Ah, that was a mistake on my part. I pushed the docs to fix the datepicker API being missing, but forgot to check for APIs that should have been omitted. This will all be improved when we make our docs publishing more automated.

[AndreyJS]

With mdDialogConfig the same problem

[lucasalmeida92]

So there is no panelClass property anymore ? How do I add a class to my dialog container?
Tks in advance ;]

[willshowell]

@lucasalmeida92 panelClass does exist in master, but has not been part of a release yet. It will be available in beta.7 which should be out sometime soon

[lucasalmeida92]

Ok so I'll look forward to that! ;] Thanks @willshowell !

[angular-automatic-lock-bot[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._}