fix(ui): update chat container size, fix stylelint rules

[kapetr]

Summary

• Updates chat container width
• Fixes stylelint issue with stylelint-plugin-logical-css plugin

Linked Issues

Closes #1816

Documentation

• No Docs Needed:

If this PR adds new feature or changes existing. Make sure documentation is adjusted accordingly. If the docs is not needed, please explain why.

[gemini-code-assist]

Summary of Changes

Hello, 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 focuses on enhancing the user interface of the chat container by adjusting its width and resolving a stylelint configuration issue. The changes ensure better visual presentation and code quality.

Highlights

• Chat Container Width: Updated the chat container width to improve the user interface.
• Stylelint Configuration: Fixed a stylelint issue related to the stylelint-plugin-logical-css plugin by updating the configuration.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• apps/agentstack-ui/src/components/layouts/Container.module.scss
  • Updated the 'md' size in the $sizes map from 768px to 800px.
• apps/agentstack-ui/src/modules/runs/chat/ChatMessagesView.tsx
  • Updated the Container size from 'sm' to 'md' for both the main container and the bottom container.
• apps/agentstack-ui/src/modules/runs/chat/ChatUserMessage.module.scss
  • Updated the font size from 14px to 16px and adjusted the line height accordingly.
• apps/lint-config/stylelint.config.js
  • Updated the stylelint configuration to include the recommended settings for stylelint-plugin-logical-css and resolve plugin loading issues.
• mise.lock
  • Added provenance information for lima and uv tools on macOS arm64 platforms.

Activity

• kapetr opened the pull request.
• kapetr updated chat container size, fixed stylelint rules.

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 updates the chat container width for a better user interface and fixes stylelint configuration for logical CSS properties. The UI changes appear correct and as intended. I've found a potential issue in the stylelint configuration update where the ignore options for certain CSS properties were not carried over, which could lead to new linting warnings. I've provided a suggestion to fix this.

[PetrBulanek]

These two occurrences must also be updated. :)