0.1.16

[arhtudormorar]

Summary

• Bump version to 0.1.16 with accessibility improvements
• Add part attributes to Button and AddressTable components for improved external styling capabilities
• Add part attributes to Pagination component elements
• Fix typo in CHANGELOG.md for helpers export entry
• Remove unused import from tsconfig.utils.json

[gemini-code-assist]

Summary of Changes

Hello @arhtudormorar, 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 advances the project to version 0.1.16, primarily by enhancing the customizability and potential accessibility of several UI components. This is achieved through the strategic addition of part attributes to elements within the Button, AddressTable, and Pagination components, which allows external stylesheets to target and style internal parts of shadow DOM components. A minor CSS styling fix was also applied to ensure correct pseudo-element rendering.

Highlights

• Version Update: The project version has been updated to "0.1.16".
• Button Component Styling: The Button component now includes a part="button" attribute, facilitating external styling.
• AddressTable Component Styling: Key elements within the AddressTable component, such as the label wrapper, address display, and pagination wrapper, have been augmented with part attributes for enhanced external styling capabilities. Additionally, the internal Button component within AddressTable now exports its button part as access-button.
• Pagination Component Styling: Various elements within the Pagination component, including navigation angles and individual page items, have been equipped with part attributes for improved customizability.
• CSS Pseudo-element Fix: A CSS styling fix was implemented in pagination.styles.ts to ensure proper rendering of pseudo-elements by explicitly adding content-[""] to the paginationItemBefore class.

🧠 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.

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 bumps the version to 0.1.16 and introduces part attributes to several components (Button, AddressTable, Pagination) to allow for greater style customization from outside the shadow DOM. The changes are well-implemented. I've left one suggestion on the CHANGELOG.md to make the description of the changes more accurate and comprehensive.

[gemini-code-assist]

The changelog entry is not fully comprehensive. The changes also add part attributes to the Pagination component, which should be mentioned. Additionally, while styling can be used for accessibility, the primary purpose of part attributes is for external styling. Consider rephrasing for clarity and accuracy, as reflected in the pull request description.

Suggested change

	- [Add part attributes to Button and AddressTable components for improved accessibility](https://github.com/multiversx/mx-sdk-dapp-ui/pull/297)
	- [Add part attributes to Button, AddressTable, and Pagination components for improved external styling capabilities](https://github.com/multiversx/mx-sdk-dapp-ui/pull/297)