Lock on entity translation level instead on entity level

Translation lock should only be available if conflict module exists or similar functionality is implemented in core.

Till then only enable this option if conflict is enabled. Otherwise user will have conflicts again or thinks this resolution is already provided by this module.

This should fix the current tests.

New tests would be nice, but not sure if I get to it soon :/

Fixing test and doing some coding standards love.

+++ b/content_lock.module
@@ -81,8 +81,16 @@ function content_lock_form_alter(&$form, FormStateInterface $form_state, $form_i
+    // This hook function is called twice, first when the form loads
+    // and second when the form is submitted.
+    // Only perform set and check for lock on initial form load.
+    $userInput = $form_state->getUserInput();
+    if (!empty($userInput)) {
+      return;
+    }
+

This was removed in #2912023: Show the lock message after form rebuld.

Everything else looks good to me. Will test it now

Oh, forgot to merge 8.x-1.x into my dev branch again.

Fixed this now. Also fixed an issue that entity_operations are not working anymore.

+++ b/content_lock.module
@@ -299,10 +300,15 @@ function content_lock_entity_operation(EntityInterface $entity) {
+        'langcode' => $this->isTranslationLockEnabled($entity_type) ? $entity->language()->getId() : LanguageInterface::LANGCODE_NOT_SPECIFIED,

That's not possible here

$this is not allowed. We are not in object context here

And thats why we have reviews ;)
Thanks a lot.

Fixed #14

It seems that it doesn't work for me.

What i did:

1. Installed a site on english
2. Added german as a second language
3. Enabled content_translation, conflict and content_lock
4. Added content translation for my article on admin/config/regional/content-language
5. Created a second user
6. Created one article as admin and stay on that articles edit page
7. Logged in as user 2. Tried to add a translation, that works, but the edit form is still locked

Ok, it was my fault. Seems to work. Very nice

Thank you. Thats a very nice feature

Damn, i think we missed an update hook, because we changed the schema.

We have 1500 installations, we need an update hook. I am fine with adding it to #2916747: Consider the form operation when locking