Now that nodes are converted to EntityNG we should make sure in rest.module that they work in the REST API as expected. I think testing deletion should be easy, we can add that to the existing test case. Maybe also read/GET. Create/POST and Update/PATCH might be trickier and could uncover some node related issues, so that might get separate test methods (or classes).

#20 node-tests-1972116-20.patch24.68 KBklausi
PASSED: [[SimpleTest]]: [MySQL] 57,761 pass(es).
[ View ]
#20 node-tests-1972116-20-interdiff.txt3.22 KBklausi
#17 node-tests-1972116-17.patch22.55 KBklausi
PASSED: [[SimpleTest]]: [MySQL] 57,283 pass(es).
[ View ]
#17 node-tests-1972116-17-interdiff.txt2.48 KBklausi
#15 node-tests-1972116-15.patch20.37 KBklausi
PASSED: [[SimpleTest]]: [MySQL] 56,764 pass(es).
[ View ]
#15 comment-validation-2002158-15-interdiff.txt1.1 KBklausi
#13 node-tests-1972116-13.patch16.58 KBklausi
FAILED: [[SimpleTest]]: [MySQL] 56,991 pass(es), 3 fail(s), and 0 exception(s).
[ View ]
#13 node-tests-1972116-13-interdiff.txt3.14 KBklausi
#11 node-tests-1972116-11.patch15.34 KBklausi
PASSED: [[SimpleTest]]: [MySQL] 56,467 pass(es).
[ View ]
#11 node-tests-1972116-11-interdiff.txt2.21 KBklausi
#4 node-tests-1972116-4.patch13.14 KBklausi
PASSED: [[SimpleTest]]: [MySQL] 57,054 pass(es).
[ View ]
#4 node-tests-1972116-4-interdiff.txt9.46 KBklausi
#1 node-tests-1972116-1.patch4.29 KBklausi
PASSED: [[SimpleTest]]: [MySQL] 54,796 pass(es).
[ View ]


Status:Active» Needs review
new4.29 KB
PASSED: [[SimpleTest]]: [MySQL] 54,796 pass(es).
[ View ]

Here is a patch that adds tests for GET and DELETE, which is relatively easy and uses the same code as entity_test.

Status:Needs review» Reviewed & tested by the community

Looks like a reasonable way to expand test coverage. We can do more in followups.

Status:Reviewed & tested by the community» Needs review

Heh, maybe I should have mentioned that this patch is not finished yet :-)

We need tests for PATCH and POST here as well, since Lin already mentioned problems when POSTing nodes.

new9.46 KB
new13.14 KB
PASSED: [[SimpleTest]]: [MySQL] 57,054 pass(es).
[ View ]

Adapted creation test to also include nodes, works fine in this minimal version of POSTing the node type and title only.

TODO: test coverage for PATCH.

I did some manual POST testing with nodes and it is important that you remove all special fields from your content type that you want to test. Taxonomy term reference fields, file fields etc. do not work right now.

Here is a cURL example request I used successfully to create a primitive article that has a title and a body field:

curl --include --request POST --cookie SESSf722138df952ff0f3000137055cb16f4=OKpUoonJqjekZCKQUw5ZM4kGX--nJ6AN0qWTLZLobrA --header 'Content-type: application/hal+json' --header 'X-CSRF-Token: zC9uOOrmCbOEqDXhgdcEqgFD2ft6RGJzKpTCfUzSJHw' http://drupal-8.localhost/entity/node --data-binary '{"_links":{"self":{"href":"http://drupal-8.localhost/node/"},"type":{"href":"http://drupal-8.localhost/rest/type/node/article"}},"type":[{"value":"article"}],"title":[{"value":"test title"}]}'

You have to replace the cookie and the CSRF token (can be retrieved at /rest/session/token) accordingly.

I also had to disable comment module to make this work.

The offending code in comment module is this:

function comment_node_insert(EntityInterface $node) {
  // Allow bulk updates and inserts to temporarily disable the
  // maintenance of the {node_comment_statistics} table.
  if (variable_get('comment_maintain_node_statistics', TRUE)) {
        'last_comment_uid' => $node->uid,

If the $node doesn't have a uid set, then there is an integrity constraint violation because it can't be NULL.

REST module should probably set the $node->uid anyway, using the user id of the user who made the request. I don't think we want a user with POST privileges to be able to create a node and assign it to another uid.

Priority:Normal» Major

This sounds like it's probably at least major, given the number of bugs digging into this is uncovering.

#4: node-tests-1972116-4.patch queued for re-testing.

new2.21 KB
new15.34 KB
PASSED: [[SimpleTest]]: [MySQL] 56,467 pass(es).
[ View ]

Implemented a test case for nodes with comment module enabled, so that a missing node author does not trigger errors in comment module.

What do we want to test for PATCH regarding nodes?

For PATCH, the simplest is to change required fields like created, author, title. More advanced PATCH could be handled in these tests or in serialization (e.g. date fields, entity ref fields, etc.).

new3.14 KB
new16.58 KB
FAILED: [[SimpleTest]]: [MySQL] 56,991 pass(es), 3 fail(s), and 0 exception(s).
[ View ]

PATCH is really broken right now, I added a test case to demonstrate that a title field change fails.

The problem is that serializer (the denormalier) uses entity_create() for building the node object. During that default values get applied to the fields, which we do not want in the PATCH case. We only want to update some specific fields on an existing node.

We could pass the node ID to serializer and it could perform an entity_load() to get the existing node, but then we don't know which fields where updated later in REST module in order to perform field access checks on them. So we could also move the access checks into serializer, but then it does way to much business logic outside the scope of just deserializing.

One more time I realize that we need #1965780: Add EntityDiff entity type for handling PATCH requests.

Status:Needs review» Needs work

The last submitted patch, node-tests-1972116-13.patch, failed testing.

Status:Needs work» Needs review
new1.1 KB
new20.37 KB
PASSED: [[SimpleTest]]: [MySQL] 56,764 pass(es).
[ View ]

New idea: use a deserialization context to indicate PATCH request data. The denormalizer can use that to simply unset all fields on the prepared entity and then fill it with incoming data. That is one way to get rid of the default values.

This would also mean that we don't need an extra EntityDiff approach. What do you think?

I'm at NYC Camp, so haven't had a chance to do a full review yet, but the basic principle sounds good to me.

Do you have a test to ensure that a field can be deleted using the empty array, and that a field that wasn't in the request does not get deleted? I thought we got rid of the distinction between empty values and NULL values in Portland.

new2.48 KB
new22.55 KB
PASSED: [[SimpleTest]]: [MySQL] 57,283 pass(es).
[ View ]

Deleting field with an empty array works as we expect, we already have a test case for that. I added a test to make sure that omitted fields in a PATCH request do not delete the field.

I also documented the "request_method" context array key on the denormalizer.

Status:Needs review» Reviewed & tested by the community

This looks good to me, and much needed.

Status:Reviewed & tested by the community» Needs work

+++ b/core/modules/hal/lib/Drupal/hal/Normalizer/EntityNormalizer.phpundefined
@@ -89,6 +101,15 @@ public function denormalize($data, $class, $format = NULL, array $context = arra
+    // Special handling for PATCH: destroy all possible default values that
+    // might have been set on entity creation. We want an "empty" entity that
+    // will only get filled with fields from the data array.
+    if (isset($context['request_method']) && $context['request_method'] == 'patch') {
+      foreach ($entity as $field_name => $field) {
+        $entity->set($field_name, NULL);
+      }
+++ b/core/modules/rest/lib/Drupal/rest/Tests/NodeTest.phpundefined
@@ -0,0 +1,76 @@
+    // Reload the node from the DB and check if the title was correctly updated.
+    $node = entity_load('node', $node->id(), TRUE);
+    $this->assertEqual($node->get('title')->get('value')->getValue(), $new_title);

Shouldn't we be testing the code that prevents changing of values to default here too. That is, shouldn't we be testing other values have not changed.

+++ b/core/modules/rest/lib/Drupal/rest/Tests/UpdateTest.phpundefined
@@ -65,8 +65,18 @@ public function testPatchUpdate() {
+    // Make sure that the field does not get deleted if it is not present in the
+    // PATCH request.
     $normalized = $serializer->normalize($patch_entity, $this->defaultFormat);
+    unset($normalized['field_test_text']);
+    $serialized = $serializer->encode($normalized, $this->defaultFormat);
+    $this->httpRequest('entity/' . $entity_type . '/' . $entity->id(), 'PATCH', $serialized, $this->defaultMimeType);
+    $this->assertResponse(204);
+    $entity = entity_load($entity_type, $entity->id(), TRUE);
+    $this->assertNotNull($entity->field_test_text->value. 'Test field has not been deleted.');

So I removed the code in EntityNormalizer::denormalize concerning the patch method (see above) and ran Drupal\rest\Tests\UpdateTest - which still passes. I thought this might be testing that code? I guess not - which means we have no test coverage of it.

Status:Needs work» Needs review
new3.22 KB
new24.68 KB
PASSED: [[SimpleTest]]: [MySQL] 57,761 pass(es).
[ View ]

Thanks Alex, very good points! I added an explicit test for the HAL denormalizer + a check for the UUID in the node test.

Status:Needs review» Needs work
Issue tags:-WSCCI

The last submitted patch, node-tests-1972116-20.patch, failed testing.

Status:Needs work» Needs review
Issue tags:+WSCCI

#20: node-tests-1972116-20.patch queued for re-testing.

Status:Needs review» Reviewed & tested by the community

more test coverage is good. back to rtbc.

Status:Reviewed & tested by the community» Fixed

Committed cde3c7d and pushed to 8.x. Thanks!

Automatically closed -- issue fixed for 2 weeks with no activity.