[iOS Clean] Added dialogs UI support.

ios/clean/chrome/browser/ui/dialogs/dialog_mediator+internal.h

+// Copyright 2017 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef IOS_CLEAN_CHROME_BROWSER_UI_DIALOGS_DIALOG_MEDIATOR_INTERNAL_H_
+#define IOS_CLEAN_CHROME_BROWSER_UI_DIALOGS_DIALOG_MEDIATOR_INTERNAL_H_
+
+#import "ios/clean/chrome/browser/ui/dialogs/dialog_mediator.h"
+
+#import "ios/clean/chrome/browser/ui/commands/dialog_commands.h"
+
+@class DialogButtonItem;
+@class DialogTextFieldItem;
+
+// DialogMediator functionality exposed to subclasses.

[marq (ping after 24h), 2017/06/14 10:52:15]

Document that these methods/properties do nothing by default, and that
subclasses should override them.

[kkhorimoto, 2017/06/23 06:24:18]

Done.

+@interface DialogMediator (Internal)<DialogDismissalCommands>
+
+// The dispatcher passed on initialization.
+@property(nonatomic, readonly, strong) CommandDispatcher* dispatcher;
+
+// The title to provide to the consumer.

[marq (ping after 24h), 2017/06/14 10:52:15]

Should these just be readonly properties?

[kkhorimoto, 2017/06/23 06:24:18]

The main reason was that I couldn't decide on what ARC annotation to use.  The
implementation of these functions return autoreleased values or NSString
literals.  I could make these readonly weak properties, but it seems kind of odd
to use a weak property for a factory method.

+- (NSString*)dialogTitle;
+
+// The message to provide to the consumer.
+- (NSString*)dialogMessage;
+
+// The DialogButtonItems to provide to the consumer.
+- (NSArray<DialogButtonItem*>*)buttonItems;
+
+// The DialogTextFieldItems to provide to the consumer.
+- (NSArray<DialogTextFieldItem*>*)textFieldItems;
+
+@end
+
+#endif  // IOS_CLEAN_CHROME_BROWSER_UI_DIALOGS_DIALOG_MEDIATOR_INTERNAL_H_