@Headers annotation produces unexpected newline in generated code by ksp plugin

[Robotxm]

Ktorfit version

2.2.0

What happened and how can we reproduce this issue?

For this function in my network interface:

@GET("https://example.com")
@Headers("User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36 Edg/132.0.0.0")
suspend fun example(): String

It is converted to code below by ksp plugin:

override suspend fun example(): String {
  val _ext: HttpRequestBuilder.() -> Unit = {
      method = HttpMethod.parse("GET")
      url{
      takeFrom("https://example.com")
      }
      headers{
      append("User-Agent", "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML,
          like Gecko) Chrome/132.0.0.0 Safari/537.36 Edg/132.0.0.0")
      } 
      }
  val _typeData = TypeData.createTypeData(
  typeInfo = typeInfo<String>(),
  )
  return _helper.suspendRequest(_typeData,_ext)!!
}

The User-Agent field contains an unexpected newline, which results in a compilation error.

What did you expect to happen?

No newline will be generated.

Is there anything else we need to know about?

No response

[Foso]

Thank you for the report!

[Thijsiez]

There is a pretty big chance this is a KotlinPoet side effect. I've seen it wrap like this with longer generated lines in my project :)

[AntsyLich]

This has actually been fixed upstream https://square.github.io/kotlinpoet/changelog/#version-200

KotlinPoet 1.x used to replace space characters with newline characters whenever a given line of code exceeded the length limit. This usually led to better code formatting, but could also lead to compilation errors in generated code. Non-breaking spaces could be marked by the · character, but the discoverability of this feature wasn’t great.

KotlinPoet 2.0 does not wrap spaces, even if the line of code they occur in exceeds the length limit. The newly introduced ♢ character can be used to mark spaces that are safe to wrap, which can improve code formatting. The · character has been preserved for compatibility, but its behavior is now equivalent to a regular space character.