EPILIBS-187: Wrap API Endpoints: Powerpoint

[zephyr-c]

EPILIBS-187

adds powerpointAdapter wrapping the powerpoint endpoints

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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. ↩

[gemini-code-assist]

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.

[sparklerfish]

Looks solid and matches the API accurately; overall nothing actually wrong with it but I did have a stylistic/readability suggestion in powerpoint.ts.

The package-lock conflicts can be handled by resetting to the version from master and doing a clean install, since this PR doesn't actually change any dependencies. On your branch:

git checkout master -- package-lock.json
git rebase master      # or merge master, whichever you prefer
npm ci                 # installs from the lockfile without rewriting it

This is also on me, I'll update the installation instructions in the README to use npm ci where relevant so npm version inconsistencies don't make a new lockfile unnecessarily.

Good to merge after that!