Merge pull request #310 from MunyayLLC/renovate/viem-2.x36f2b98cef0b03e2d89d8eee5316ea228524f141 Update dependency viem to v2 #313
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
[WIP] Update various existing features for improvement
[WIP] Add FUNDING.yml file to repository
…ssues [WIP] Automatically assign sponsorship inquiries to owner
…-b638-a3ba453eadbf [WIP] [BUG]
…s-issue [WIP] Fix compatibility issues in COMPATIBILITY.md and FUNDING.yml
…tibility [WIP] Fix compatibility issues in FUNDING.yml
[WIP] Update compatibility documentation for FUNDING.yml
…iles [WIP] Update COMPATIBILITY.md and FUNDING.yml files
…tions [WIP] Configure instructions for Copilot in repository
…support-md [WIP] Remove internal notes from SUPPORT.md file
…-a497-110c7bf52ae7 [WIP] [Setup]
…kflow [WIP] Add GitHub Actions workflow for Copilot integration
[WIP] Update quick-setup.sh script
…ytics-i-c7hkv6 Install Vercel Web Analytics Integration
Created a template for a custom agent configuration.
Reviewing your PR now. Feedback on the way! |
![roomote[bot]](https://avatars.githubusercontent.com/in/1546624?s=60&v=4){kind=small}
Comment on lines
+16
to
+162
| README.md# OnChainTestKit - Enterprise Web3 Testing Framework | ||
|
|
||
| [](https://github.com/MunyayLLC/onchaintestkit/actions/workflows/ci-complete.yml) | ||
| [](https://github.com/MunyayLLC/onchaintestkit/actions/workflows/copilot-setup.yml) | ||
| [](https://codecov.io/gh/MunyayLLC/onchaintestkit) | ||
| [](LICENSE) | ||
| [](https://slsa.dev) | ||
|
|
||
| Enterprise-grade end-to-end testing toolkit for Web3 applications with built-in Methttps://stackblitz.com/~/github.com/MunyayLLC/https-github.com-joe10832-onchaintestkitnpm install @reown/appkit @reown/appkit-adapter-wagmi wagmi viem @tanstack/react-query# Enterprise-Ready Software Engineering Project | ||
|
|
||
| Welcome to the **Enterprise-Ready Software Engineering Project**. This repository is designed for professional development in Python, Java, and C++ with a focus on enterprise-grade solutions, scalability, and maintainability. | ||
|
|
||
| --- | ||
|
|
||
| ## 🚀 Business Focus | ||
|
|
||
| This project is tailored for **business enterprise-ready** solutions, ensuring professional-grade software engineering practices. It emphasizes: | ||
|
|
||
| - **Scalability**: Designed to handle enterprise-level workloads. | ||
| - **Maintainability**: Code structured for long-term use and collaboration. | ||
| - **Integration**: Seamless integration with existing enterprise systems. | ||
|
|
||
| --- | ||
|
|
||
| ## 🧑💻 Your Role | ||
|
|
||
| - **Role Type**: `{role_type}` expert in `{domain}` | ||
| - **Focus Area**: `{key_skill_area}` | ||
|
|
||
| As a contributor, your expertise in `{domain}` will help shape the success of this project. Focus on `{key_skill_area}` to ensure high-quality contributions. | ||
|
|
||
| --- | ||
|
|
||
| ## 📜 Code Guidelines | ||
|
|
||
| ### General Guidelines | ||
| - Use **language-specific conventions** for Python, Java, and C++. | ||
| - Follow **design patterns** and **best practices** for enterprise software. | ||
| - Optimize for **performance**, **readability**, and **scalability**. | ||
|
|
||
| ### Python | ||
| - Follow [PEP 8](https://peps.python.org/pep-0008/) for coding standards. | ||
| - Use type hints and docstrings for better readability. | ||
| - Write unit tests using `unittest` or `pytest`. | ||
|
|
||
| ### Java | ||
| - Adhere to [Oracle's Java Code Conventions](https://www.oracle.com/java/technologies/javase/codeconventions-introduction.html). | ||
| - Use Maven or Gradle for dependency management. | ||
| - Write JUnit tests for all major components. | ||
|
|
||
| ### C++ | ||
| - Follow [Google's C++ Style Guide](https://google.github.io/styleguide/cppguide.html). | ||
| - Use `CMake` for build configuration. | ||
| - Ensure memory safety and avoid undefined behavior. | ||
|
|
||
| --- | ||
|
|
||
| ## 🔧 Integration | ||
|
|
||
| This project is designed to integrate seamlessly with enterprise systems. Key integration points include: | ||
|
|
||
| - **APIs**: RESTful APIs for communication between services. | ||
| - **Databases**: Support for relational and NoSQL databases. | ||
| - **CI/CD Pipelines**: Automated testing and deployment workflows. | ||
|
|
||
| --- | ||
|
|
||
| ## 📚 Further Reading | ||
|
|
||
| - [Python Best Practices](https://realpython.com/) | ||
| - [Java Design Patterns](https://java-design-patterns.com/) | ||
| - [C++ Modern Practices](https://isocpp.org/) | ||
|
|
||
| --- | ||
|
|
||
| For questions or support, please open an issue or contact the project maintainer.# GitHub Copilot Configuration & Setup | ||
|
|
||
| Welcome to AI-powered pair programming with GitHub Copilot! This guide will help you quickly onboard and configure Copilot for use with Python, Java, and C++ projects in this repository. | ||
|
|
||
| --- | ||
|
|
||
| ## 1. Enable Copilot for Your GitHub Account | ||
|
|
||
| 1. Ensure you have a [GitHub Copilot license](https://github.com/features/copilot). | ||
| 2. Go to **Settings > Copilot** in your GitHub account and enable Copilot for your user or organization. | ||
|
|
||
| --- | ||
|
|
||
| ## 2. Install the Copilot Extension | ||
|
|
||
| Copilot is available for popular editors: | ||
|
|
||
| - **Visual Studio Code**: [Copilot for VS Code](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) | ||
| - **JetBrains IDEs** (IntelliJ, PyCharm, CLion, etc.): [Copilot for JetBrains](https://plugins.jetbrains.com/plugin/17718-github-copilot) | ||
| - **Neovim**: [Copilot for Neovim](https://github.com/github/copilot.vim) | ||
|
|
||
| Install the extension and sign in with your GitHub account. | ||
|
|
||
| --- | ||
|
|
||
| ## 3. Project-Specific Setup | ||
|
|
||
| ### Python | ||
|
|
||
| - Use a virtual environment (`python -m venv venv`). | ||
| - Ensure `requirements.txt` or `pyproject.toml` is present for dependency management. | ||
| - Copilot works best with clear docstrings and type hints. | ||
|
|
||
| ### Java | ||
|
|
||
| - Ensure your project has a proper `pom.xml` (Maven) or `build.gradle` (Gradle) configuration. | ||
| - Use standard directory layouts (`src/main/java`, `src/test/java`). | ||
| - Document classes and methods for better Copilot context. | ||
|
|
||
| ### C++ | ||
|
|
||
| - Use a `CMakeLists.txt` or relevant build configuration file. | ||
| - Organize code in `include/` and `src/` directories. | ||
| - Comment header files and provide signature documentation. | ||
|
|
||
| --- | ||
|
|
||
| ## 4. Best Practices for Copilot | ||
|
|
||
| - Write descriptive comments and docstrings—Copilot uses them for smarter suggestions. | ||
| - Break up large files and functions for better context. | ||
| - Use meaningful variable and function names. | ||
| - Regularly review and refactor Copilot's code for security and correctness. | ||
|
|
||
| --- | ||
|
|
||
| ## 5. Troubleshooting | ||
|
|
||
| - If Copilot suggestions are not relevant, add more context or comments. | ||
| - For editor-specific troubleshooting, refer to the [Copilot Docs](https://docs.github.com/en/copilot/getting-started-with-github-copilot). | ||
|
|
||
| --- | ||
|
|
||
| ## 6. Further Reading | ||
|
|
||
| - [GitHub Copilot Documentation](https://docs.github.com/en/copilot) | ||
| - [Onboarding Guide](../README.md#onboarding) | ||
| - [Contribution Guide](../CONTRIBUTING.md) | ||
|
|
||
| --- | ||
|
|
||
| For questions or support, open an issue or contact your team lead. |
There was a problem hiding this comment.
The .github/FUNDING.yml file is malformed. Lines 16-162 contain markdown documentation content (project descriptions, Copilot setup guides, Python/Java/C++ guidelines) that should not be in a FUNDING.yml file. This file should only contain funding platform configuration keys (github, patreon, open_collective, etc.) with their associated values. The current content will cause the GitHub funding button to fail or display incorrectly. This entire section from line 16 onwards needs to be removed, leaving only the standard YAML funding configuration.
Fix it with Roo Code or mention @roomote and request a fix.
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
Brief description of the changes in this PR.
Type of Change
Changes Made
Testing
Test Commands Run
npm run lint- All linting checks passnpm run build- Project builds successfullynpm run test- All tests passNew Tests Added
Documentation
Wallet Compatibility
If this PR affects wallet functionality, confirm testing with:
Configuration Changes
If this PR changes configuration APIs:
Breaking Changes
If this is a breaking change:
Checklist
Additional Context
Add any additional context, screenshots, or information that would help reviewers understand the changes.
Related Issues
Closes #(issue number)
Related to #(issue number)