Add helper trait to provide type-hinting for zend-view

[thexpand]

In favor of the following proposal: zendframework/zend-view#102

[thexpand]

@froschdesign Travis build has failed with something like a timeout? Is there anything that we can do to re-run it or something?

[froschdesign]

This is an important enhancement for developers and should be mentioned in the documentation.

[froschdesign]

Btw. Please use the develop branch for new features.

https://github.com/zendframework/zend-i18n/blob/master/docs/CONTRIBUTING.md#what-branch-to-issue-the-pull-request-against

[thexpand]

@froschdesign The IntlDateFormatter class is used, but the ext-intl extension is not required in composer.json. The whole repository uses it, actually, so I think it's a good idea to add it (maybe in another PR, because it is a breaking change?)

[froschdesign]

@thexpand Already there as suggestion:

https://github.com/zendframework/zend-i18n/blob/c6c465ad5c7c9b93304f2a2832c9b4deafb3fcdf/composer.json#L33-L34

[thexpand]

@froschdesign I suggest adding the documentation as a sub-section of the main section View Helpers. We could name the sub-section: Auto-completion in templates or IDE auto-completion in templates. Which place do you think will be more appropriate - at the top or at the bottom of the view helpers? https://docs.zendframework.com/zend-i18n/view-helpers/

[froschdesign]

@thexpand

Which place do you think will be more appropriate - at the top or at the bottom of the view helpers?

At the top. (Later we will split the entire page and then we can also add an introduction like in other components,)

[thexpand]

@froschdesign I've added the documentation. Can you take a look so that I can copy-paste it to the other repositories' PRs for the HelperTrait?

[thexpand]

I have moved it in a block quote and applied the headings indentation - looks better now :+1:

[weierophinney]

Thanks, @thexpand!