docs: fix javadoc formatting #343
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
One of the descriptions of the supported connection properties missed an ending </code> block, which caused the entire formatting to be incorrect. Fixes #342
google-cla bot added the cla: yes 
product-auto-label bot added the api: spanner 
Codecov Report
@@ Coverage Diff @@ ## master #343 +/- ## ========================================= Coverage 71.35% 71.35% Complexity 1114 1114 ========================================= Files 24 24 Lines 3474 3474 Branches 531 531 ========================================= Hits 2479 2479 Misses 778 778 Partials 217 217
Continue to review full report at Codecov.
|
elharo approved these changes Feb 3, 2021
thiagotnunes approved these changes Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
One of the descriptions of the supported connection properties missed an ending
</code>block, which caused the entire formatting to be incorrect.Fixes #342