components/google_slides/actions/create-presentation/create-presentation.mjs (1)

7-7: Version bump looks correct – please sync changelog

The increment to 0.0.3 aligns with the other action bumps in this PR. Just make sure the public changelog / marketplace description is updated so users understand what changed.

components/google_slides/actions/merge-data/merge-data.mjs (1)

7-7: Patch bump to 0.0.2

Looks fine; just double-check that any new placeholder-handling features introduced elsewhere are reflected in the docs for this action.

components/google_slides/common/constants.mjs (1)

1-143: Comprehensive shape types definition looks good.

The extensive list of shape types covers all major categories (basic shapes, arrows, flowchart symbols, callouts, etc.) and follows consistent naming conventions. This centralized approach will ensure consistency across actions that create shapes.

Consider adding JSDoc documentation to describe the purpose and usage:

+/**
+ * Supported shape types for Google Slides page elements
+ * @see https://developers.google.com/workspace/slides/api/reference/rest/v1/presentations/requests#ShapeType
+ */
 export const SHAPE_TYPES = [

components/google_slides/actions/insert-text/insert-text.mjs (1)

37-47: Consider adding validation for the text parameter.

While the text parameter is required, consider adding length validation or format checks to provide better user experience.

 text: {
   type: "string",
   label: "Text",
   description: "The text to insert",
+  validate: (value) => {
+    if (!value?.trim()) {
+      throw new Error("Text cannot be empty or contain only whitespace");
+    }
+    return true;
+  },
 },

components/google_slides/actions/create-image/create-image.mjs (1)

26-30: Add URL validation for the image parameter.

Consider validating that the URL is accessible and points to a valid image format to prevent API errors.

 url: {
   type: "string",
   label: "URL",
   description: "The URL of the image to insert",
+  validate: (value) => {
+    try {
+      new URL(value);
+      return true;
+    } catch {
+      throw new Error("Please provide a valid URL");
+    }
+  },
 },

components/google_slides/actions/delete-slide/delete-slide.mjs (1)

27-31: Consider adding confirmation for destructive operation.

While the implementation is correct, consider adding a confirmation step or warning for this destructive operation to prevent accidental slide deletion.

 async run({ $ }) {
+  // Note: This is a destructive operation that cannot be undone
   const response = await this.googleSlides.deleteObject(this.presentationId, this.slideId);
   $.export("$summary", `Successfully deleted slide with ID: ${this.slideId}`);
   return response.data;
 },

Alternatively, consider adding a confirmation prop:

 props: {
   googleSlides,
   presentationId: { /* existing */ },
   slideId: { /* existing */ },
+  confirm: {
+    type: "boolean",
+    label: "Confirm Deletion",
+    description: "Confirm that you want to permanently delete this slide",
+    default: false,
+  },
 },

components/google_slides/actions/create-page-element/create-page-element.mjs (1)

57-70: Consider using number type for translation properties.

While translation values are often whole numbers, the Google Slides API accepts decimal values for precise positioning. Consider changing to number type for flexibility.

     translateX: {
-      type: "integer",
+      type: "number",
       label: "Translate X",
-      description: "The translation of the shape on the x-axis",
+      description: "The translation of the shape on the x-axis in points (1/72 of an inch)",
       default: 0,
       optional: true,
     },
     translateY: {
-      type: "integer",
+      type: "number",
       label: "Translate Y",
-      description: "The translation of the shape on the y-axis",
+      description: "The translation of the shape on the y-axis in points (1/72 of an inch)",
       default: 0,
       optional: true,
     },

components/google_slides/actions/create-slide/create-slide.mjs (1)

42-43: Add null-safe response parsing.

While the error handling is good, the response parsing could be more defensive against unexpected API response structures.

-      $.export("$summary", `Successfully created slide with ID: ${response.data.replies[0].createSlide.objectId}`);
+      const objectId = response.data?.replies?.[0]?.createSlide?.objectId;
+      if (!objectId) {
+        throw new ConfigurationError("Unexpected API response: slide ID not found");
+      }
+      $.export("$summary", `Successfully created slide with ID: ${objectId}`);

components/google_slides/google_slides.app.mjs (1)

137-146: Consider adding JSDoc documentation for the deleteObject method.

The deleteObject method name is generic and could benefit from documentation explaining that it can delete both slides and page elements.

+    /**
+     * Deletes an object (slide or page element) from a presentation
+     * @param {string} presentationId - The ID of the presentation
+     * @param {string} objectId - The ID of the object to delete (can be a slide ID or page element ID)
+     * @returns {Promise} The API response
+     */
     deleteObject(presentationId, objectId) {

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro