Skip to content

Developer Documentation Improvement: Add Example to Base Code #550

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
acul71 opened this issue Mar 28, 2025 · 1 comment
Closed

Developer Documentation Improvement: Add Example to Base Code #550

acul71 opened this issue Mar 28, 2025 · 1 comment

Comments

@acul71
Copy link
Contributor

acul71 commented Mar 28, 2025

Description

Overview

This issue proposes an enhancement to the developer documentation for py-libp2p. The goal is to add a clear example of how to integrate an example into the base code. This addition will help contributors understand how to extend and utilize the library in a practical scenario.

Motivation

  • Clarity for Developers: Provide guidance on how to implement and run examples that illustrate key features of the library.
  • Onboarding New Contributors: Lower the learning curve for new developers by offering a hands-on example.
  • Improved Documentation: Enhance the developer experience and encourage more contributions by clarifying best practices.

Proposed Changes

  1. Documentation Update:

    • Add a new section to the developer documentation titled "Adding an Example to the Base Code".
    • Include step-by-step instructions on where and how to add examples.
    • Provide code snippets and comments explaining the rationale behind each step.
  2. Example Addition:

    • Create a sample example that demonstrates a common use-case.
    • Ensure the example is minimal, clear, and follows the established coding conventions of py-libp2p.
  3. Testing and Validation:

    • Include instructions on how to run the example.
    • Suggest any tests that should accompany the example to verify its functionality.

Implementation Details

  • Location: The new documentation section should be integrated within the existing developer guide.
  • Formatting: Use Markdown for clear, readable formatting. Ensure code blocks are properly highlighted.
  • References: Link to relevant sections in the codebase and existing documentation for consistency.

Next Steps

  • Review and discuss the proposal with maintainers.
  • Finalize the documentation changes.
  • Submit a Pull Request once consensus is reached.

Additional Notes

If there are any questions or further suggestions, please comment on this issue so that we can refine the proposal before the PR is submitted.

Motivation

Clarity for Developers

Current Implementation

Missing

Are you planning to do it yourself in a pull request ?

Yes

@pacrob
Copy link
Member

pacrob commented Apr 2, 2025

closed by #551

@pacrob pacrob closed this as completed Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants