Diagnostics are poor when misconfiguration leads to operation-specific configuration being null

[nosan]

see more here

[wilkinsona]

Thanks for the PR. As mentioned in my comment on the Spring Boot issue, the problem isn't specific to WebTestClient. If a change is to be made here, it should be done for MockMvc and REST Assured as well. Would you like to do that as part of this proposal?

[nosan]

@wilkinsona sure, I had some thoughts about this.

[nosan]

@wilkinsona I added Assert.state(configuration != null) for RestAssured, MockMvc and WebTestClient, but I have a problem with a build:

> Task :restNotesGrailsGradle
> Task :clean
> Task :compileJava NO-SOURCE
> Task :compileGroovy FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileGroovy'.
> javax/servlet/http/HttpServletRequest

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 6s
2 actionable tasks: 2 executed

> Task :restNotesGrailsGradle FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':restNotesGrailsGradle'.
> Process 'command './gradlew'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Also, I had tried to build a master branch, and It was not built as well.

Have I missed something?

[wilkinsona]

Thanks for your patience, @nosan, and for your first contribution to Spring REST Docs. The proposed changes have now been merged into master.

[nosan]

Everything is ok :) Thanks