Skip to content

EPILIBS-187: Wrap API Endpoints: Powerpoint#158

Open
zephyr-c wants to merge 1 commit intomasterfrom
EPILIBS-187
Open

EPILIBS-187: Wrap API Endpoints: Powerpoint#158
zephyr-c wants to merge 1 commit intomasterfrom
EPILIBS-187

Conversation

@zephyr-c
Copy link
Copy Markdown

@zephyr-c zephyr-c commented Mar 23, 2026

EPILIBS-187

adds powerpointAdapter wrapping the powerpoint endpoints

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 introduces a new powerpointAdapter to the library, enabling programmatic interaction with PowerPoint API endpoints. This adapter provides functionalities to generate PowerPoint presentations from templates, either returning the generated file as binary data or as a stream, facilitating integration with applications requiring dynamic presentation generation. The changes also include necessary type definitions and integration into the library's export structure, along with dedicated unit tests to ensure functionality.

Highlights

  • New PowerPoint Adapter: A new powerpointAdapter has been introduced to interact with PowerPoint API endpoints, enabling programmatic generation of presentations.
  • API Functions: The adapter includes generate and stream functions for creating PowerPoint files from templates, returning binary data or a streaming response, respectively.
  • Type Definitions: Comprehensive TypeScript interfaces have been defined for PowerPoint document structures, including data points, chart series, charts, tables, pictures, environments, slides, and documents.
  • Dependency Updates: Dependency metadata in package-lock.json was updated, primarily adjusting peer and devOptional flags for various packages.
  • Unit Tests: Dedicated unit tests for the new powerpointAdapter have been added, covering HTTP methods, authorization, URL construction, request body, and header handling.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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.

Copy link
Copy Markdown
Contributor

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

Choose a reason for hiding this comment

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

Code Review

The pull request introduces a new powerpointAdapter module, including its implementation in src/adapters/powerpoint.ts with interfaces for PowerPoint document structures and functions to generate (via PUT) and stream (via POST) PowerPoint files from templates. This adapter is integrated into the main library exports and thoroughly tested in tests/powerpoint.spec.js. Review comments suggest improving the documentation for the BinaryData interface and providing a more detailed explanation of the document parameter in the generate function's JSDoc to enhance code understanding.

Comment on lines +101 to +107
export interface BinaryData {
encoding: 'HEX' | 'BASE_64';
data: unknown;
encryption?: 'AES' | null;
name?: string | null;
content_type?: string | null;
contentType?: unknown;
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

Consider adding a brief description of what BinaryData represents, especially the contentType field, to improve code understanding.

Comment on lines +134 to +158
/**
* Generates a PowerPoint file from a template and returns it as binary data (JSON-encoded)
* Base URL: PUT `https://forio.com/api/v3/{ACCOUNT}/{PROJECT}/powerpoint/{TEMPLATE_DIRECTORY}/{TEMPLATE_PATH}`
*
* @example
* import { powerpointAdapter } from 'epicenter-libs';
* const binaryData = await powerpointAdapter.generate('MODEL', 'en-US-debrief-template.pptx', {
* output: 'debrief-slides.pptx',
* environment: {},
* slides: [
* {
* number: 1,
* environment: {
* tables: [{ name: 'Leaderboard', data: [['Rank', 'Name', 'Score']] }],
* },
* },
* ],
* });
*
* @param templateDirectory Directory where the template is stored: 'DATA' or 'MODEL'
* @param templatePath Path to the template file within the directory
* @param document Document shadow defining the output filename, environment, and slides
* @param [optionals] Optional arguments; pass network call options overrides here.
* @returns promise that resolves to the generated PowerPoint as BinaryData
*/
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

The JSDoc for the generate function could benefit from a more detailed explanation of the document parameter, including the structure and purpose of the environment and slides properties. This would help users understand how to define the desired PowerPoint document structure.

Comment thread tests/powerpoint.spec.js
Comment on lines +155 to +157
it('Should not have any untested methods', () => {
const actualMethods = getFunctionKeys(powerpointAdapter);
expect(actualMethods).toEqual(testedMethods);
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

This test ensures that all methods in the adapter are tested. Consider adding a comment explaining why this test is important for maintainability.

@zephyr-c zephyr-c requested a review from sparklerfish March 23, 2026 22:37
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