And the asciidoc extension should probably added t...
# spring
s
c
How would you suggest going about collaborating with @ienoobong on the PR?
i
There was a comment by Andy yesterday https://github.com/spring-projects/spring-boot/pull/18017#issuecomment-526593835 Hence I’m not sure how to proceed
Kindly advice @sdeleuze
c
This seems like if there are runnable files referenced in the documentation we should be creating kotlin versions that are also runnable and test to reference. If there aren't runnable versions of the Java it should be better to do that it the same time.
s
@corneil @ienoobong Andy is ok if we provide Kotlin code snippets as runnable code as shown here : https://github.com/spring-projects/spring-boot/issues/6313#issuecomment-231035872. Any chance you could modify current PR into runnable Kotlin code to see if that works combined with Java/Kotlin tabs ?
c
What is the best way for multiple people to contribute to a PR?
s
I guess @ienoobong could add you as contributor on his fork, but for now I would suggest you to fork it and point to your commit in a PR comment.
c
Okay will do so.
i
Looks good, will take that approach
Added you @corneil
c
Thanks
Do you think it would be best to have a separate profile in the Maven build for the Kotlin files which excludes the java files to ensure they can live side by side with same names?
@sdeleuze @awilkinson?
s
I usually avoid same names (for test for example)
See for example
c
That makes it simpler.
@ienoobong
s
Yeah if that possible that will avoid some troubles
So something like
Kotlin*
prefix will be fine
Maybe Andy will polish it differently for Boot but for the PR that will be fine IMO
i
Ok, thanks!