Skip to content

[INTEG-3250] Google Docs App skeleton#10227

Merged
ryunsong-contentful merged 3 commits intomasterfrom
INTEG-3250
Nov 7, 2025
Merged

[INTEG-3250] Google Docs App skeleton#10227
ryunsong-contentful merged 3 commits intomasterfrom
INTEG-3250

Conversation

@ryunsong-contentful
Copy link
Copy Markdown
Contributor

@ryunsong-contentful ryunsong-contentful commented Nov 3, 2025

Purpose

Function Backend

  • Key starting point would beapps/google-docs/functions/createEntriesFromDocument.ts
  • Scaffold out the Google Docs app so that the team can easily recognize where to work
  • Allow people to critique and understand the architecture
  • This doesn't mean this cannot change, however the basic principles should be obvious (separate AI Agents, separate services for creating entries and assets, separate observation services)

Frontend

  • Keep it simple and just link the relevant JIRA tickets
  • We don't know the exact designs yet so keep all of the locations and minimize cleanup until we see the designs

Before Merging

  • Check the App Function Invocation time limit with Tundra and make sure the right architecture is in place before merging
  • Get feedback from the LLM as a service team

@ryunsong-contentful ryunsong-contentful requested a review from a team as a code owner November 3, 2025 21:39
@ryunsong-contentful ryunsong-contentful changed the title INTEG-3250 Google Docs App skeleton [INTEG-3250] Google Docs App skeleton Nov 3, 2025
@ryunsong-contentful ryunsong-contentful force-pushed the INTEG-3250 branch 8 times, most recently from 36dc81f to 2f03e0e Compare November 4, 2025 20:17
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.

Looks like a great start! I added a few comments about some minor things that jumped out at me.

"preview": "vite preview",
"test": "vitest",
"create-app-definition": "contentful-app-scripts create-app-definition",
"deploy": "contentful-app-scripts upload --ci --bundle-dir ./build --organization-id ${DEFINITIONS_ORG_ID} --definition-id {3EaGZUMKRKVZUyrcoNJ4o4} --token ${CONTENTFUL_CMA_TOKEN}",
Copy link
Copy Markdown
Contributor

@primeinteger Adrian Meyer (primeinteger) Nov 4, 2025

Choose a reason for hiding this comment

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

Is this a real app def id in the deploy script? I dont think it needs to be surrounded in curly braces.

"upload-ci": "contentful-app-scripts upload --ci --bundle-dir ./build --organization-id $CONTENTFUL_ORG_ID --definition-id $CONTENTFUL_APP_DEF_ID --token $CONTENTFUL_ACCESS_TOKEN",
"upsert-actions": "contentful-app-scripts upsert-actions --ci --organization-id $CONTENTFUL_ORG_ID --definition-id $CONTENTFUL_APP_DEF_ID --token $CONTENTFUL_ACCESS_TOKEN",
"build:functions": "contentful-app-scripts build-functions --ci",
"deploy:dev": "source .env && contentful-app-scripts upload --ci --bundle-dir ./build --organization-id \"$DEFINITIONS_ORG_ID\" --definition-id {653vTnuQw3j5onU1tUoH6t} --token \"$CONTENTFUL_CMA_TOKEN\"",
Copy link
Copy Markdown
Contributor

@primeinteger Adrian Meyer (primeinteger) Nov 4, 2025

Choose a reason for hiding this comment

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

Is this a real app def id in the deploy:dev script? I dont think it needs to be surrounded in curly braces here either.

},
{
"id": "prompt",
"name": "Prompt fromt he user",
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.

Typo in the prompt name 👀

{
"id": "prompt",
"name": "Prompt fromt he user",
"type": "String",
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.

Should the prompt type be Symbol here?

Comment on lines +16 to +21
interface ContentTypeParserConfig {
openaiApiKey: string;
modelVersion: string;
jsonData: any;
document: any;
}
Copy link
Copy Markdown
Contributor

@primeinteger Adrian Meyer (primeinteger) Nov 4, 2025

Choose a reason for hiding this comment

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

Should this type be named DocumentParserConfig instead? The content type parser function already has an interface with this name.

@ryunsong-contentful ryunsong-contentful merged commit d96467d into master Nov 7, 2025
15 checks passed
@ryunsong-contentful ryunsong-contentful deleted the INTEG-3250 branch November 7, 2025 17:50
ryunsong-contentful added a commit that referenced this pull request Nov 7, 2025
* feat: initialize google-docs app

* feat: add functions and backend for google-docs

* feat: fill out instructions and jira ticket numbers to the backend function skeleton for google-docs
ryunsong-contentful added a commit that referenced this pull request Nov 7, 2025
* feat: initialize google-docs app

* feat: add functions and backend for google-docs

* feat: fill out instructions and jira ticket numbers to the backend function skeleton for google-docs
ryunsong-contentful added a commit that referenced this pull request Nov 10, 2025
* [INTEG-3250] Google Docs App skeleton (#10227)

* feat: initialize google-docs app

* feat: add functions and backend for google-docs

* feat: fill out instructions and jira ticket numbers to the backend function skeleton for google-docs

* fix: google doc skeleton issues
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.

2 participants