Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Jonesy
Copy link
Contributor

@Jonesy Jonesy commented Dec 13, 2023

Description

Types of changes

Adds improved inline Go documentation to help new developers understand methods and structs as needed, which is prominently displayed via LSPs in editors like Visual Studio Code (see screenshot). This includes the ability to add example code, links to specific files, etc.

image
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation (non-breaking change with enhancements to documentation)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have checked that unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

See https://tip.golang.org/doc/comment for further details and examples of other documentation formatting that can be added in subsequent new code added to the repo.

@Jonesy Jonesy requested a review from ikethecoder December 13, 2023 21:27
@github-actions
Copy link

πŸ”” Friendly reminder: The following reviewers still need to review this PR: @ikethecoder

PS: @sdqdadat

4 similar comments
@github-actions
Copy link

πŸ”” Friendly reminder: The following reviewers still need to review this PR: @ikethecoder

PS: @sdqdadat

@github-actions
Copy link

πŸ”” Friendly reminder: The following reviewers still need to review this PR: @ikethecoder

PS: @sdqdadat

@github-actions
Copy link

πŸ”” Friendly reminder: The following reviewers still need to review this PR: @ikethecoder

PS: @sdqdadat

@github-actions
Copy link

πŸ”” Friendly reminder: The following reviewers still need to review this PR: @ikethecoder

PS: @sdqdadat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants