Generalize A2UI Actions (v0.9)

[jacobsimionato]

Generalizes the concept of A2UI actions by moving the action schema from the Button component to common_types.json as a shared Action type.

This new Action type supports:

1. The existing server-side action structure (object with name and context).
2. A new local action capability, specified via a function parameter (string or object).

Example of local action usage: "action": "openUrl(${/url})"

This allows components other than Button to potentially define actions in the future, and enables local client-side behavior.

[gemini-code-assist]

Code Review

This pull request generalizes the A2UI action concept by moving it to a shared type in common_types.json and adding support for local client-side actions. The changes to the JSON schemas are well-structured and the refactoring in standard_catalog.json is correct. The documentation has also been updated to reflect these new capabilities.

My review includes two main points. First, the examples in the updated documentation for the new action types on Button components are incorrect as they use a non-existent text property instead of the required child property. Second, the pull request is missing tests for the new local action functionality, which is required by the repository's contribution guidelines. Addressing these points will improve the accuracy of the documentation and ensure the new feature is properly tested.

[gemini-code-assist]

This pull request introduces a significant new feature: local actions, with both an object and a string shorthand form. However, there are no new test cases being added to verify this new functionality. Adding tests for the new local action formats is important to ensure they are parsed and handled correctly by clients.

References

1. The repository style guide requires that code changes are accompanied by tests. This change adds a new feature without corresponding tests. ^(link)

[gemini-code-assist]

The Button component examples in the "Defining Actions" section are incorrect. According to the standard_catalog.json schema, Button does not have a text property. Instead, it requires a child property which should be the ID of a child component (like Text). This issue is present in the "Server Actions", "Local Actions (String Shorthand)", and "Local Actions (Object Definition)" examples.

For example, the server action snippet should be structured like this:

{
  "component": "Button",
  "child": "submit_button_label",
  "action": {
    "name": "submit_form",
    "context": {
      "itemId": "123"
    }
  }
}

...where submit_button_label would be the ID of a Text component defined separately (e.g., {"id": "submit_button_label", "component": "Text", "text": "Submit"}).

Please correct all three examples to align with the Button component's schema.

Suggested change

	"component": "Button",
	"text": "Submit",
	"component": "Button",
	"child": "submit_button_label",