-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Use runnable code to generate main documentation samples #6313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
That and actually testing them would be nice to ensure backward compatibility. |
I've done it in REST Docs too. It's not too arduous. |
I've made a (tiny) start on this. See in ccaa19d. |
philwebb
added a commit
that referenced
this issue
Feb 4, 2021
Add `pending-extract=true` to source blocks to help us identify those that need to be extracted to a real source file. See gh-6313
philwebb
added a commit
that referenced
this issue
Feb 4, 2021
Add additional dependencies useful for the example code. See gh-6313
philwebb
added a commit
that referenced
this issue
Feb 4, 2021
philwebb
added a commit
that referenced
this issue
Feb 5, 2021
philwebb
added a commit
that referenced
this issue
Mar 9, 2021
Update extracted samples to make use of code folding and chomping. See gh-6313
philwebb
added a commit
that referenced
this issue
Mar 13, 2021
philwebb
added a commit
that referenced
this issue
Apr 24, 2021
philwebb
added a commit
that referenced
this issue
Apr 24, 2021
philwebb
added a commit
that referenced
this issue
Apr 25, 2021
philwebb
added a commit
that referenced
this issue
Apr 26, 2021
philwebb
added a commit
that referenced
this issue
Apr 30, 2021
philwebb
added a commit
that referenced
this issue
May 4, 2021
philwebb
added a commit
that referenced
this issue
May 4, 2021
Marking this one as complete but we might need to do the same with Gradle/Maven docs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should look at using running sample code imported into our
.adoc
files to prevent issues like #6312. Spring Security has done this already.The text was updated successfully, but these errors were encountered: