Add regression tests and document writeRaw* design decision

- Add testWriteContextCurrentNameIsUpdatedForEveryProperty: verifies that
  addValueNode calls writeContext.writeValue() so _gotPropertyId is reset
  after each value, keeping currentName() correct for multi-property objects
- Add testWritePropertyIdUpdatesWriteContext: verifies that writePropertyId
  calls writeContext.writeName() when supportIntegerKeys=true, so
  streamWriteContext().currentName() reflects the integer key
- Document writeRaw* / writeRawValue* design decision in preexisting-issues.md:
  current behavior (delegate to addValueNode like writeString) satisfies the
  contract and is preferable to throwing UnsupportedOperationException

Author: komamitsu

msgpack-jackson3/src/test/java/org/msgpack/jackson/dataformat/MessagePackGeneratorTest.java

@@ -1207,4 +1207,46 @@ public void testSerializedStringMethods()
         assertEquals(5, written);
         assertArrayEquals("hello".getBytes(java.nio.charset.StandardCharsets.UTF_8), baos.toByteArray());
     }
+
+    // Regression: addValueNode must call writeContext.writeValue() so that the Jackson write
+    // context resets _gotPropertyId after each value. Without it, the second writeName() in the
+    // same object finds _gotPropertyId still set from the first writeName() and returns false
+    // without updating currentName(), leaving streamWriteContext().currentName() stale.
+    @Test
+    public void testWriteContextCurrentNameIsUpdatedForEveryProperty()
+            throws IOException
+    {
+        ByteArrayOutputStream baos = new ByteArrayOutputStream();
+        JsonGenerator generator = factory.createGenerator(ObjectWriteContext.empty(), baos);
+        generator.writeStartObject();
+
+        generator.writeName("alpha");
+        generator.writeNumber(1);
+
+        generator.writeName("beta");
+        assertEquals("beta", generator.streamWriteContext().currentName());
+        generator.writeNumber(2);
+
+        generator.writeEndObject();
+        generator.close();
+    }
+
+    // Regression: writePropertyId() must call writeContext.writeName() when supportIntegerKeys
+    // is true. Without it, streamWriteContext() never learns a name was written, so currentName()
+    // returns null and any downstream code relying on context state (e.g. duplicate-name
+    // detection, error messages) sees wrong state.
+    @Test
+    public void testWritePropertyIdUpdatesWriteContext()
+            throws IOException
+    {
+        MessagePackFactory intKeyFactory = new MessagePackFactory().setSupportIntegerKeys(true);
+        ByteArrayOutputStream baos = new ByteArrayOutputStream();
+        JsonGenerator generator = intKeyFactory.createGenerator(ObjectWriteContext.empty(), baos);
+        generator.writeStartObject();
+        generator.writePropertyId(42L);
+        assertEquals("42", generator.streamWriteContext().currentName());
+        generator.writeString("value");
+        generator.writeEndObject();
+        generator.close();
+    }
 }

plans/preexisting-issues.md

@@ -72,6 +72,26 @@ buffer) into a `StringBuilder`, matching the pattern already used in the len<0 b
 The len<0 path (StringBuilder + 1024-char chunk) still allocates an extra copy vs.
 `CharArrayWriter`, but the overhead is minor and not worth optimizing at this layer.
 
+### 6. `writeRaw*` / `writeRawValue*` — FYI, no action needed
+
+**File:** `msgpack-jackson3/.../MessagePackGenerator.java`
+
+CBORGenerator and SmileGenerator both throw `UnsupportedOperationException` for all
+`writeRaw*` / `writeRawValue*` overloads. This was flagged in code review as something
+MessagePackGenerator should match.
+
+After investigation, the current implementation (which delegates to `addValueNode`, same
+as `writeString`) is correct and need not change:
+
+- The `writeRaw` contract requires: no escaping, no separators, content preserved
+  unchanged. All three are satisfied — MessagePack has no JSON-style escaping or
+  separators, and the text is packed verbatim via `packString`.
+- CBOR/Smile throwing is a design choice, not a technical requirement. They could
+  equally implement it as "write as a text value" — they chose to be strict instead.
+- Our lenient approach (degrade gracefully to `writeString` behaviour) is just as
+  defensible, and avoids breaking callers that use `writeRaw` as a `writeString`
+  synonym.
+
 ---
 
 ## msgpack-jackson pre-existing issues