Resolve fatal error in repository generator

[AntonEvers]

Description

Both InputException and NoSuchEntityException require a Phrase object as first constructor argument
PHP Fatal error: Uncaught TypeError: Argument 1 passed to Magento\\Framework\\Exception\\InputException::__construct() must be an instance of Magento\\Framework\\Phrase, string given

Fixed Issues (if relevant)

1. Can't delete last item in cart if Minimum Order is Enable  #6151

Manual testing scenarios

1. auto-generate a repository
2. call the get method without a parameter

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[ishakhsuvarov]

@ajpevers Thanks for this PR. We are currently working on deprecating repository generation feature and materialization of all existing auto-generated repositories, so please do not rely heavily on this approach

[AntonEvers]

@ishakhsuvarov ooh, good that you mention it. In that case I won't use it in my own code.

[AntonEvers]

@ishakhsuvarov do you have a good example of a repository class in the Magento code base? On http://devdocs.magento.com/guides/v2.1/extension-dev-guide/service-contracts/design-patterns.html the interfaces CustomerRepositoryInterface, AddressRepositoryInterface and GroupRepositoryInterface are mentioned as good examples, but 2 of them use the deprecated save() method directly on the entity objects. GroupRepositoryInterface uses a save method on the resource model. Is that the way to go with repositories?

[ishakhsuvarov]

@ajpevers Yes, currently this is an applicable way to go, however this may be swapped out for a better way (from the architectural perspective) in the future.