feat(schema): add optional operator field to Wiki schema

[Yomzy2223]

• What kind of change does this PR introduce? feature

• What is the current behavior? there's currently no way to track which editor makes use of Sophia

• What is the new behavior (if this is a feature change)? this PR adds an optional operator field to the Wiki schema to allows for tracking users who publish through Sophia

[changeset-bot]

🦋 Changeset detected

Latest commit: f830dca

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@everipedia/iq-utils	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello @Yomzy2223, 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 capability to track the specific user (referred to as an 'operator') responsible for publishing content through the Sophia platform. By adding an optional operator field to the Wiki schema, the system can now maintain a clear record of who initiated a publication, enhancing accountability and auditing for content management workflows.

Highlights

• Schema Enhancement: An optional operator field has been added to the Wiki schema.
• User Tracking: This new field allows for tracking which editor makes use of Sophia when publishing content.
• Data Type: The operator field is an object containing a string id, making it consistent with existing user and author fields.

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

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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

This pull request introduces an optional operator field to the Wiki schema, which is a useful addition for tracking editors. The change is implemented correctly. I have one suggestion to improve code maintainability by refactoring a duplicated schema definition.

[gemini-code-assist]

The structure z.object({ id: z.string() }) is now duplicated across user, author, and the newly added operator fields. To improve maintainability and adhere to the DRY (Don't Repeat Yourself) principle, I suggest creating a reusable schema for this structure.

You could define a new schema in the 'Supporting Schemas' section, similar to other base types in this file:

export const UserReference = z.object({ id: z.string() });

Then, you can use it for user, author, and operator fields like so:

user: UserReference,
author: UserReference,
operator: UserReference.optional(),

This will make the Wiki schema cleaner and easier to manage if the user reference structure ever needs to be changed.