Implement hook_help for module.

Follow Help Text standards https://www.drupal.org/docs/develop/documenting-your-project/help-text-standards

Uses section is not there.

Working on it.

Made changes according to standards. Interdiff added.

@dhruveshdtripathi, Thanks for patch, it works well i checked it with simplytest.me. PFA

Thanks for the patch. A couple things:

• While there really shouldn't be a require_once() call at the top of the module like there is, that call should stay at the top. The added youtube_help() should at least come after that call and before youtube_menu().
• If we're going to add this, it should be added to Drupal 8 as well. Please port the patch so both could be committed at the same time.

Thanks again!

Agreed! Working on that.

Moved hook_help section between require_once and hook_menu. About Drupal8. I'll be working on it after D7 gets committed. We'll move this issue to D8 after it gets committed to D7. Suggested me any other changes if needed.

Thanks!

Looking good. Just a few Drupal code standards to sort out and this looks done.

1. +++ b/youtube.module
   @@ -4,9 +4,32 @@
   + * Implementation of hook_help().
   

   Format should be "* Implements hook_foo().", "* Implements hook_foo_BAR_ID_bar() for xyz_bar().", "* Implements hook_foo_BAR_ID_bar() for xyz-bar.html.twig.", "* Implements hook_foo_BAR_ID_bar() for xyz-bar.tpl.php.", or "* Implements hook_foo_BAR_ID_bar() for block templates."

2. +++ b/youtube.module
   @@ -4,9 +4,32 @@
   +      $output .= '<p>' . t('For more information, see the <a href="https://www.drupal.org/project/youtube">Youtube Field module</a>.' . '</p>');
   

   The closing paragraph tag should not be in the t().

3. +++ b/youtube.module
   @@ -4,9 +4,32 @@
   +      $output .= '<h5>' . t('The module provides following Display Types: ') . '</h5>';
   

   Translatable strings should not start or end with white space.

+++ b/youtube.module
@@ -4,9 +4,32 @@
+ * Implements of hook_help().

Almost there.

Lose the "of" and it's done.

Just a note on Code Standards; The Coder module is very handy in checking these. It works from the website and can integrate into external tools like PHP CodeSniffer which, in turn, can integrate into your preferred code editor.

I find it very handy for this sort of thing.

This comment also tweaks the commit details a bit. I just read Commit messages - providing history and credit and noticed that the automated details get a little lost after multiple people start tweaking the patch.

Fixed the minor nit pick

@harsha012, Thanks for Providing patch, Now all the errors are clear & your patch works correctly for me.

Indeed, it is a minor nit pick. But they're called Standards for a reason. Automated tools can't really sit there and go "meh, not a big deal".

This looks good to me now too. +1 for RTBC.

@harsha012 thanks for your time on this. :)

Changed a little and commited.