Skip to content

Ci2 - #3234

Closed
polina-c wants to merge 5 commits into
mainfrom
ci2
Closed

Ci2#3234
polina-c wants to merge 5 commits into
mainfrom
ci2

Conversation

@polina-c

Copy link
Copy Markdown
Collaborator

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces support for A2UI protocol version 1.0 across the a2ui_agent and a2ui_core packages, which includes updating catalog providers, capability negotiation, and adding a MessageProcessor.forAgent for outbound payload validation. Additionally, the handwritten Express parser has been replaced with an ANTLR-generated parser. The review feedback highlights several instances across multiple files where explicit type annotations on loop variables should be omitted to avoid triggering the omit_obvious_local_variable_types lint.

throw A2uiCatalogError('No catalog states a protocol version.');
}
final Set<A2uiProtocolVersion> versions = {
for (final CatalogApi catalog in catalogs)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the omit_obvious_local_variable_types lint.

Suggested change
for (final CatalogApi catalog in catalogs)
for (final catalog in catalogs)
References
  1. In Dart, avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the 'omit_obvious_local_variable_types' lint.

);
}
final A2uiProtocolVersion version = catalogsProtocolVersion([
for (final CatalogConfig config in catalogs) config.catalog,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the omit_obvious_local_variable_types lint.

Suggested change
for (final CatalogConfig config in catalogs) config.catalog,
for (final config in catalogs) config.catalog,
References
  1. In Dart, avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the 'omit_obvious_local_variable_types' lint.

}) =>
MessageProcessor<T>(
catalogs: [
for (final Catalog<T, FunctionApi> catalog in catalogs)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the omit_obvious_local_variable_types lint.

Suggested change
for (final Catalog<T, FunctionApi> catalog in catalogs)
for (final catalog in catalogs)
References
  1. In Dart, avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the 'omit_obvious_local_variable_types' lint.

// The listener throws at the first error, so the tree is complete.
final ProgramContext program = parser.program();
return [
for (final StatementContext statement in program.statements())

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the omit_obvious_local_variable_types lint.

    for (final statement in program.statements())
References
  1. In Dart, avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the 'omit_obvious_local_variable_types' lint.

CallNode _call(String source, CallContext call) {
final args = <ExpressNode>[];
final kwargs = <String, ExpressNode>{};
for (final ArgContext arg in call.args()) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the omit_obvious_local_variable_types lint.

  for (final arg in call.args()) {
References
  1. In Dart, avoid adding an explicit type annotation to a loop variable when the iterable already has an explicit type argument, as this can trigger the 'omit_obvious_local_variable_types' lint.

@polina-c polina-c closed this Oct 15, 2026
@github-project-automation github-project-automation Bot moved this from Todo to Done in A2UI Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant