In my iOS project I have a set of custom textfields, e.g. for password entry.
As an example, such textfields can contain additional views and logic - for example, show or hide a password with a press of a button.
Since this logic is not used anywhere outside the textField, I have an idea to create a PasswordTextFieldController and set the textField as its only view.
The show/hide password behavior goes to the PasswordTextFieldController and the controller itself is used as a child view controller with the help of View Controller Containment.
As all the relevant logic has been encapsulated, I could reuse the same PasswordTextFieldController during both signup and login.
Are there any drawbacks in this approach?