Set default block label

[mzueva]

Set default block label

[gemini-code-assist]

Summary of Changes

Hello @mzueva, 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 improves the user experience by setting a descriptive default label for a block component, guiding users to select a dataset. Concurrently, it incorporates routine updates to various project dependencies, upgrading several core @milaboratories and @platforma-sdk packages to their newer versions to maintain compatibility and leverage recent improvements.

Highlights

• Default Block Label: The default label for a block has been updated from an empty string to 'Select Dataset', providing a more informative placeholder for users.
• Dependency Updates: Several @milaboratories and @platforma-sdk packages have been updated to their latest versions, ensuring the project benefits from the newest features and bug fixes.

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 sets a more descriptive default block label, which is a nice improvement. However, it also bundles dependency updates for several packages. The pull request title and description only mention the label change, which can be misleading. For better maintainability and easier reviews, it's recommended to separate dependency updates into their own pull requests. I've left a specific comment with a suggestion on how to address this.

[gemini-code-assist]

This pull request updates several dependencies in the workspace catalog. While keeping dependencies up-to-date is important, the title of this PR ("Set default block label") doesn't mention these changes. This can make it difficult to track dependency updates in the project's history.

It's generally better to handle dependency updates in a separate pull request with a clear title (e.g., "chore(deps): update dependencies"). This makes reviews more focused and rollbacks safer.

Could you please either:

1. Update the title and description of this PR to reflect the dependency updates.
2. (Preferred) Revert the dependency updates from this PR and create a separate one for them.