[vector_math] Document CircleGenerator API

[faisalansari0367]

Adds public API docs for CircleGenerator (class and createCircle) and removes the public_member_api_docs ignore for circle_generator.dart, following the same pattern as #12 and #22.

Part of the ongoing vector_math doc migration tracked in flutter/flutter#186827.

Validation

• dart analyze
• dart test (252 tests)
• dart pub global run flutter_plugin_tools validate --packages=vector_math
• dart pub global run flutter_plugin_tools format --packages=vector_math --fail-on-change --no-swift
• dart pub global run flutter_plugin_tools publish-check --packages=vector_math --allow-pre-release

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

No new tests were added because the implementation diff only changes documentation comments. The complete existing package test suite passes.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request documents the public CircleGenerator API in the vector_math package. It removes the ignore rule for public member API documentation in circle_generator.dart, adds documentation comments to the CircleGenerator class and its createCircle method, and updates the package version to 2.4.3 in pubspec.yaml and CHANGELOG.md. There are no review comments, and I have no feedback to provide.

[stuartmorgan-g]

Thank you for your contribution! Because of the volume of PRs we receive, we require that new contributors use our checklist to guide them through critical steps in creating a Flutter PR. This PR's description is missing that checklist, so it is being marked as a Draft.

Please edit the PR description to add the checklist, then ensure that you have completed all of the steps. Once you've done that, please mark the PR as ready for review.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[gemini-code-assist]

Code Review

This pull request updates the vector_math package to version 2.4.3 by documenting the public CircleGenerator API. Specifically, it removes the ignore_for_file directive for public member API documentation in circle_generator.dart and adds documentation comments to the CircleGenerator class and the createCircle method. The CHANGELOG.md and pubspec.yaml files are updated to reflect the version bump. There are no review comments, so there is no additional feedback to provide.

[faisalansari0367]

@stuartmorgan-g kindly review it.

[stuartmorgan-g]

Please don't ping individual people to request reviews. This PR will be assigned to one of the package owners for review during our regular triage, as with any other PR.