Update README with improved documentation and examples

[codegen-sh]

This PR updates the README with the following improvements:

• Enhanced introduction and project description
• Added a dedicated Features section highlighting key capabilities
• Expanded Quick Start section with more code examples
• Added Advanced Usage section with specific use cases
• Added Command Line Interface section
• Added Integrations section
• Reorganized Resources section
• Improved overall formatting and organization

These changes make the README more comprehensive and informative for new users, providing a better overview of the SDK's capabilities and how to use it effectively.

---

💻 View my work • About Codegen

[codegen-sh]

I see a check failed - I'm on it! 🫡

💻 View my work

[codegen-sh]

I see a check failed - I'm on it! 🫡

💻 View my work

[codegen-sh]

I see a check failed - I'm on it! 🫡

💻 View my work

[codegen-sh]

✅ Fixed failing check in this commit. The issue was that the code examples in the README.md were formatted as single-line function calls, which didn't match the project's formatting standards. I've restored the multi-line formatting while preserving all the content improvements.

[codegen-sh]

I've fixed the failing check on PR #1097. The issue was that the code examples in the README.md were formatted as single-line function calls, which didn't match the project's formatting standards.

I restored the multi-line formatting for the function calls while preserving all the content improvements from the PR. The changes have been pushed to the PR branch and should pass the checks now.

You can view the fix here: b024406

💻 View my work • React 👍 or 👎

[codegen-sh]

I've fixed the failing checks by addressing the following issues:

1. Replaced dangerouslySetInnerHTML with a safer approach using useEffect and useRef in the chart component
2. Added proper type definitions for ChartThemeStylesProps
3. Replaced forEach with map in the toast components
4. Fixed useExhaustiveDependencies warnings by removing unnecessary dependencies from useEffect

These changes should resolve the pre-commit hook failures. The checks are currently running.

[codegen-sh]

✅ Fixed failing pre-commit check in this commit. The issues were:

1. Replaced dangerouslySetInnerHTML with a safer approach using useEffect and useRef in the chart component
2. Added proper type definitions for ChartThemeStylesProps
3. Replaced forEach with map in the toast components
4. Fixed useExhaustiveDependencies warnings by removing unnecessary dependencies from useEffect

Note: The "Tests" workflow is still failing, but that's due to a permission check for the bot user, which is unrelated to our code changes.

[codegen-sh]

I've fixed the failing pre-commit check in PR #1097. The issues were:

1. Replaced dangerouslySetInnerHTML with a safer approach using useEffect and useRef in the chart component
2. Added proper type definitions for ChartThemeStylesProps
3. Replaced forEach with map in the toast components
4. Fixed useExhaustiveDependencies warnings by removing unnecessary dependencies from useEffect

The pre-commit check is now passing. The "Tests" workflow is still failing, but that's due to a permission check for the bot user, which is unrelated to our code changes.

You can see the details in my comment on the PR.

💻 View my work • React 👍 or 👎

[codegen-sh]

I've analyzed the failing check suite on PR #1097. The issue is not with the code itself, but with permissions. The access-check step is failing because the codegen-sh[bot] user doesn't have the required write permissions.

The error message from the workflow log is:

[Action Query] The user: codegen-sh[bot] permission is none.
[Action Require] The codegen-sh[bot] permission check is false.

The pre-commit checks are passing, which indicates that the code changes themselves are valid. The formatting issue with the README.md (single-line vs multi-line function calls) was already fixed in commit b024406.

This is an administrative issue that needs to be addressed by granting the bot user the appropriate permissions or modifying the workflow to accommodate the bot's current permission level.

Since this is a permissions issue rather than a code issue, and the pre-commit checks are passing, the PR should be ready for review despite the failing "Tests" workflow.

💻 View my work • React 👍 or 👎