lyne-components icon indicating copy to clipboard operation
lyne-components copied to clipboard

chore: missing 'sbb-' prefix in stories

Open DavideMininni-Fincons opened this issue 2 weeks ago • 1 comments

DavideMininni-Fincons avatar Nov 14 '25 14:11 DavideMininni-Fincons

Summary of Changes

Hello @DavideMininni-Fincons, I'm Gemini Code Assist[^1]! 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 minor but important consistency issue within the Storybook documentation. It standardizes the naming convention for several 'timetable' related components by adding the 'sbb-' prefix to their Storybook titles. This change improves the organization and discoverability of these components within Storybook, making it easier for developers to navigate and understand the component hierarchy.

Highlights

  • Storybook Title Consistency: Updated Storybook titles for several components to consistently include the 'sbb-' prefix within the 'timetable' category, ensuring standardized naming.
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 :thumbsup: and :thumbsdown: 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.


Prefixes align, Stories now are neatly grouped, Order brings clear view.

[^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[bot] avatar Nov 14 '25 14:11 gemini-code-assist[bot]

As discussed; We leave it as timetable for now.

kyubisation avatar Nov 20 '25 12:11 kyubisation