fix: correct new_artifact methods signature

[Lancetnik]

Artifact class has nullable description with default None Artifact(description: str | None = None)

But, utilities functions creates and artifact with empty description by default description=''

Release-As: 0.3.10

[gemini-code-assist]

Summary of Changes

Hello @Lancetnik, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a type inconsistency where artifact creation utility functions were defaulting the description parameter to an empty string, while the Artifact class itself allowed None. The changes ensure that these utility functions now correctly reflect the Artifact class's nullable description field by setting the default value to None, improving type consistency and clarity across the codebase.

Highlights

• Type Signature Alignment: The description parameter in new_artifact, new_text_artifact, and new_data_artifact utility functions has been updated to str | None = None, aligning with the Artifact class's nullable description field.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly updates the description parameter in artifact creation utility functions to default to None instead of an empty string, which aligns with the Artifact type definition. This is a good fix for consistency. I've left one comment regarding a necessary update to a unit test that seems to be broken by this change. Please address it to ensure the test suite passes.