Drupal 8 version for node_title_help

I have not started working on D8 version. But you can expect the D8 release by 1st April 2016.

I already have created 8.x branch. I have provided you repository access. You can push your code to 8.x branch. Please let me know once you are done so that I can create new release.

Appreciate your contribution.

Hi Makbul,

I already have started working on D8 version. You can see there is 8.x-1.x branch present in the GIT. The work is in progress. You can take a look at the code and merge your code into that branch. You do have access to commit to the branch. Please let me know once you are done so that I can test and create 8 release.

Instructions are here https://www.drupal.org/project/node_title_help_text/git-instructions

Thanks.

I already have added you as a maintainer for this module with GIT access. I prefer to keep the rights to create release and maintain project page with me. For the tagging it will start to show up once we create the first release for D8. So issue of creating D8 version for this module can be considered as feature request and can be tagged to 7.x dev release.

Hi Makbul,

Great work on D8 module. The code works perfectly as expected.
I just have one feedback, to store the help text currently \Drupal::state() is used. As per Drupal documentation

Use this to store machine-generated data, local to a specific environment that does not need deploying and does not need human editing; for example, the last time cron was run. Data which needs to be edited by humans and needs to be the same across development, production, etc. environments (for example, the system maintenance message) should use \Drupal::config() instead.

I think we should use \Drupal::config() here.

We are generating variable name based on content type and storing help text which is user generated data into those variables.

https://antistatique.net/en/we/blog/2016/06/14/drupal-8-differences-betw...
State information differs from configuration in the following ways:

1. It is specific to an individual environment.
2. You will never deploy to deploy it between environments. !! Important
3. You can reset a system, losing all state. Its configuration remains.
4. + If we use config these items can be exported using features module.

https://www.drupal.org/docs/8/api/state-api

1. It is specific to an individual environment.
2. You will never want to deploy it between environments.
3. You can reset a system, losing all state. Its configuration remains.
4. So, use State API to store transient information, that is okay to lose after a reset. Think: CSRF tokens, tracking when something non-critical last happened

I believe that the node title help text should be exportable as configuration.

Should we create a separate ticket to make the text exportable as configuration, to keep this ticket from being cluttered?

Created another ticket https://www.drupal.org/node/2895885