Features

• Pure TypeScript: Written from the ground up in pure TypeScript for type safety and modern JavaScript compatibility.
• No Dependencies: Zero external dependencies mean fewer security risks and optimal performance.
• High Performance: Efficient rendering and smooth interactions even with large datasets.
• Customizable Charts: Easily customizable chart types including candlestick, line, bar, and more.
• Interactive Tools: A suite of interactive tools for detailed analysis, including zoom, pan, and annotation capabilities.
• Responsive Design: Adaptive layout for seamless use across devices and screen sizes.
• Extensible Architecture: Designed for easy integration and extension to fit your specific needs.

This library uses kline charts as its core with lots of customizations, which is licensed under the Apache License 2.0.

Charting Platform

Contribution Guidelines

We welcome contributions from the community! Here's how you can contribute:

Code Contributions

1. Fork the Repository: Start by forking the repository to your GitHub account.
2. Create a Branch: Create a feature or bugfix branch (git checkout -b feature/your-feature-name).
3. Make Your Changes: Implement your changes, following the coding standards.
4. Commit Your Changes: Write clear and concise commit messages (git commit -m "Your message").
5. Push to Your Fork: Push the changes to your fork (git push origin feature/your-feature-name).
6. Submit a Pull Request: Open a pull request with a description of your changes.

Reporting Issues

• Search for Existing Issues: Before opening a new issue, search for existing issues to avoid duplicates.
• Open a New Issue: If no existing issue matches, open a new issue with detailed information, including steps to reproduce the issue.

Coding Standards

• Follow the Existing Code Style: Maintain consistency with the project's existing code style.
• TypeScript Best Practices: Adhere to TypeScript best practices and ensure type safety.
• Testing: Ensure that your changes are covered by tests and do not break existing tests.

Documentation

• Update Documentation: If your changes affect usage or behavior, update the documentation accordingly.
• Clear and Concise: Write documentation that is clear, concise, and easy to follow.

License

By contributing, you agree that your contributions will be licensed under the Apache License 2.0.