operation:: doesn't work after upgrading to asciidoctor 3.3.2 version

build.gradle.kts:

plugins {
	id("org.asciidoctor.base") version "3.3.2"
	id("org.asciidoctor.jvm.convert") version "3.3.2"
}
val snippetsDir by extra { file("build/generated-snippets") }
tasks {
	testI {
		outputs.dir(snippetsDir)
	}

	asciidoctor {
		sourceDir(file("$projectDir/src/docs"))
		setOutputDir(File(buildDir, "docs"))
		inputs.dir(snippetsDir)
		inputs.dir(file("src/docs"))
		attributes(mapOf("snippets" to snippetsDir))
		dependsOn(testI)
	}
}

source file

=== Get client

operation::client-get-by-id[snippets='curl-request,http-request,http-response']

resulting HTML file has following intstead of results of operation::* expansion

<h3 id="_get_client"><a class="link" href="#_get_client">Get client</a></h3>
<div class="paragraph">
<p>operation::client-get-by-id[snippets='curl-request,http-request,http-response']</p>
</div>

This worked before upgrading to latest asciidoctor plugin. When the source adoc file is opened in IntelliJ with asciidoctor plugin installed, all the snippets show up in the preview pane.

NOTE: testI is just a test task for a custom source set.

[wilkinsona]

Glad to hear you got it working. https://github.com/spring-projects/spring-restdocs/issues/680 is tracking some documentation updates to show how to configure the newer versions of the Asciidoctor Gradle Plugin.

[wilkinsona]

I’ve just checked the rest-notes-spring-hateoas sample in this repository. It uses 3.3.2 of the org.asciidoctor.jvm.convert plugin and the operation macro without any problems.

isn’t operation:: a rest-docs concept? How do I check if there is a regression?

Yes, but it’s not responsible for the macro being called. That’s done by Asciidoctor.

Looking at your example, I can’t see any sign of the spring-restdocs-asciidoctor dependency. Have you set up that dependency and configured Asciidoctor to use it? You can see an example of that in the sample that I linked to above.

If you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.