[PYG-366] 🫡 Newline in doctring of typed SDKs #470
+46
−6
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
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified Files
|
rsjr
previously approved these changes
May 6, 2025
doctrino
force-pushed
the
typed-fix-docstring
branch
from
bcc54d1 to
623220d
Compare
doctrino
force-pushed
the
typed-fix-docstring
branch
from
623220d to
ee3b460
Compare
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.
Description
Esthetic fix, ensures a newline before arguments when generating TypedSDK. Note this functionality is not exposed, those not triggering a new release.
This lack of newline causes the docstring to not render properly:
Bump