Added Charting examples

[anubrag]

• New Features

  • Expanded charting capabilities with various chart types such as bar, area, composed, funnel, line, pie, radar, and scatter charts.

• Refactor

  • Enhanced the 'nextpy' library to export a wider range of chart components and utilities.
    directories.

[coderabbitai]

Walkthrough

The project has been updated to include a .gitignore file for better version control and to introduce comprehensive charting capabilities. With the addition of charting_examples.py, the nextpy library is now utilized to showcase a variety of chart types. The xtconfig.py file has been introduced for application configuration, and the nextpy library itself has been expanded to export a suite of chart-related components.

Changes

File Path	Change Summary
.../charting-examples/.gitignore	Added to exclude specific file types and directories.
.../charting-examples/charting_examples.py	Modified to include various chart types using nextpy.
.../charting-examples/xtconfig.py	Introduced for application configuration.
nextpy/__init__.py nextpy/frontend/components/__init__.py	Expanded to export a range of chart-related components and utilities.

Poem

🎨🐇 CodeRabbit hopped along,
Tracking changes, never wrong.
Charts and configs, neat and spry,
In nextpy's world, our charts fly high! 📈🚀

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 416a801 and adcda33.

Files ignored due to path filters (2)

• app-examples/charting-examples/assets/favicon.ico is excluded by: !**/*.ico
• pyproject.toml is excluded by: !**/*.toml

Files selected for processing (5)

• app-examples/charting-examples/.gitignore (1 hunks)
• app-examples/charting-examples/charting_examples/charting_examples.py (1 hunks)
• app-examples/charting-examples/xtconfig.py (1 hunks)
• nextpy/init.py (1 hunks)
• nextpy/frontend/components/init.py (1 hunks)

Files skipped from review due to trivial changes (1)

• app-examples/charting-examples/.gitignore

Additional comments: 4

app-examples/charting-examples/xtconfig.py (1)

• 1-5: The configuration for the charting_examples application is set up correctly using the nextpy library's Config class.

nextpy/frontend/components/__init__.py (1)

• 19-19: The import of the recharts module is added correctly and is consistent with the existing structure of the file.

app-examples/charting-examples/charting_examples/charting_examples.py (1)

• 1-286: The charting examples are well-structured and follow the nextpy library's conventions for creating charts. The data structures and chart components are defined correctly, and the index function is set up appropriately to display the charts.

nextpy/__init__.py (1)

• 293-301: The _MAPPING dictionary has been updated correctly to include new chart-related components and utilities, which are necessary for the new charting functionality and consistent with the existing code structure.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 416a801 and c7c6719.

Files ignored due to path filters (2)

• app-examples/charting-examples/assets/favicon.ico is excluded by: !**/*.ico
• pyproject.toml is excluded by: !**/*.toml

Files selected for processing (6)

• app-examples/charting-examples/.gitignore (1 hunks)
• app-examples/charting-examples/charting_examples/charting_examples.py (1 hunks)
• app-examples/charting-examples/xtconfig.py (1 hunks)
• nextpy/init.py (1 hunks)
• nextpy/frontend/components/init.py (1 hunks)
• nextpy/frontend/templates/apps/hello/code/pages/graphing.py (5 hunks)

Files skipped from review as they are similar to previous changes (4)

• app-examples/charting-examples/.gitignore
• app-examples/charting-examples/charting_examples/charting_examples.py
• app-examples/charting-examples/xtconfig.py
• nextpy/frontend/components/init.py

Additional comments: 2

nextpy/frontend/templates/apps/hello/code/pages/graphing.py (1)

• 128-135: The usage of data_1 in the composed_chart function call is correct and consistent with the variable definition at the beginning of the file.

nextpy/__init__.py (1)

• 293-301: The expansion of the nextpy.frontend.components.recharts module to include a variety of chart-related components and utilities is correctly implemented. All components are added to the _MAPPING dictionary, which will make them available for import as part of the nextpy package.