fix: Change the plugin version specification method

[riscait]

🙌 What's Done

• Change the plugin version specification method
• bump to altive_lints: 2.0.0-dev.3

✍️ What's Not Done

Pre-launch Checklist

• I have reviewed my own code (e.g., updated tests and documentation)

[gemini-code-assist]

Summary of Changes

Hello @riscait, 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 refines the integration method for the altive_lints plugin by transitioning from a path-based reference to a version-based dependency. This change simplifies how the plugin is included and managed within projects, ensuring a more robust and standard approach to package usage. The update also includes necessary documentation adjustments, a version bump, and a minor internal refactoring of how lint rules are registered.

Highlights

• Plugin Specification Method: The altive_lints plugin specification has been updated from a local file path to a version-based dependency, improving maintainability and ease of use.
• Documentation Update: The README.md and altive_lints.yaml files have been updated to reflect the new version-based plugin specification method.
• Changelog and Version Bump: The CHANGELOG.md has been updated, and the package version in pubspec.yaml has been incremented to 2.0.0-dev.3.
• Code Refactoring: The main.dart file now registers lint rules by iterating over a list of AnalysisRule instances, improving code readability and organization.
• Pubspec Topics: Added more descriptive topics to pubspec.yaml for better discoverability.

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 plugin version specification method from using a local path to a version, which is a good improvement for package consumers. The changes are consistent across the pubspec.yaml, CHANGELOG.md, and configuration files. The documentation in README.md has been updated accordingly, but it now includes a hardcoded version number which could be difficult to maintain. I've suggested using a placeholder instead. Additionally, there's a nice refactoring in lib/main.dart that improves code conciseness by using forEach on a list to register lint rules.

[gemini-code-assist]

Hardcoding the version number in the documentation can become a maintenance burden, as it will need to be updated with every new release. To avoid this, consider using a placeholder like <latest_version> and instructing users to find the latest version on pub.dev.

Suggested change

	version: ^2.0.0-dev.3
	version: <latest_version>

[gemini-code-assist]

Similar to the previous comment, hardcoding the version here can lead to outdated documentation. Using a placeholder would be more maintainable in the long run.

Suggested change

	version: ^2.0.0-dev.3
	version: <latest_version>