-
Notifications
You must be signed in to change notification settings - Fork 163
Closed
Labels
advancedrequires knowledge of multiple areas in the codebase without defined steps to implement or examplesrequires knowledge of multiple areas in the codebase without defined steps to implement or examples
Description
π§ Advanced Contributors
This issue is intended for contributors who are already very familiar with the
Hiero Python SDK codebase and its architectural patterns.
You should feel comfortable:
- navigating multiple modules across
src/ - understanding and modifying core SDK abstractions
- reasoning about API design and backwards compatibility
- updating or extending tests, examples, and documentation as needed
- making changes that may affect public-facing behavior
New developers should start with
Good First Issues or Intermediate Issues first.
π Problem Description
Describe the problem here.
π‘ Proposed / Expected Solution
Describe the proposed solution here.
π§ Implementation & Design Notes
Add detailed implementation notes here.
β Acceptance Criteria
To merge this issue, the pull request must:
- Fully address the problem and design goals described above
- Maintain backwards compatibility unless explicitly approved otherwise
- Follow existing architectural and coding conventions
- Include comprehensive tests covering new and existing behavior
- Update relevant examples and documentation
- Pass all CI checks
- Include a valid changelog entry
- Use DCO and GPG-signed commits
π Additional Context, Links, or Prior Art
Optional.
coderabbitai
Metadata
Metadata
Assignees
Labels
advancedrequires knowledge of multiple areas in the codebase without defined steps to implement or examplesrequires knowledge of multiple areas in the codebase without defined steps to implement or examples