feat: extend description extraction with Returns keyword #7
Conversation
This file contains 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
axtloss
reviewed
Sep 6, 2024
|
Pallas' source code also works as a demo of Pallas itself. Can you add returns to its public functions? |
|
Do you mean adding the comments and include Yes of course, |
yup |
created an additional PR #9 |
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.
the description extraction utility now can identify and extract "Returns:" from comments in order to make returns descriptions available for parsing as suggested in this Vanilla-OS/Vib#106 (comment) conversation.
@mirkobrombin please let me know if this disturbs you more than it helps.