-
Notifications
You must be signed in to change notification settings - Fork 1
[DEV-2819] use synced response for solutions and release notes #1697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[DEV-2819] use synced response for solutions and release notes #1697
Conversation
🦋 Changeset detectedLatest commit: 4039ab2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove all file with deprecated comment
…nto DEV-2819-use-synced-response-for-solutions-and-release-notes
🎉 All dependencies have been resolved ! |
…esponse-for-solutions-and-release-notes
Jira Pull Request LinkThis Pull Request refers to the following Jira issue DEV-2819 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR migrates the data fetching strategy for solutions and release notes from direct Strapi API calls to using synced responses stored in CDN. This change enables frontend synchronization with GitBook data without requiring re-deployments.
- Removes direct Strapi API fetches for solutions, solution list pages, and release notes
- Replaces with CDN-based synced response fetching for these content types
- Adds proper error handling and validation for the new data source
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.
Show a summary per file
File | Description |
---|---|
apps/nextjs-website/src/lib/strapi/fetches/fetchSolutions.ts | Removed - no longer needed with synced response approach |
apps/nextjs-website/src/lib/strapi/fetches/fetchSolutionListPage.ts | Removed - replaced by CDN fetching |
apps/nextjs-website/src/lib/strapi/fetches/fetchReleaseNotes.ts | Removed - replaced by CDN fetching |
apps/nextjs-website/src/lib/strapi/fetches/fetchGuides.ts | Removed - replaced by CDN fetching |
apps/nextjs-website/src/lib/strapi/fetches/fetchGuideListPages.ts | Removed - replaced by CDN fetching |
apps/nextjs-website/src/lib/cmsApi.ts | Updated to use synced response functions from gitbook-docs package |
.changeset/shaggy-baths-bake.md | Documents the breaking change for version tracking |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
export const getSolutionsProps = async () => { | ||
const strapiSolutions = await fetchSolutions(buildEnv); | ||
return makeSolutionsProps(strapiSolutions); | ||
// TODO: restore this when Strapi will manage guides metadata |
Copilot
AI
Oct 8, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The TODO comment refers to 'guides metadata' but the function getSolutionsProps
is handling solutions data, not guides. The comment should be updated to reflect the correct content type.
// TODO: restore this when Strapi will manage guides metadata | |
// TODO: restore this when Strapi will manage solutions metadata |
Copilot uses AI. Check for mistakes.
jsonMetadata?: JsonMetadata | ||
) => { | ||
const strapiSolutions = await fetchSolution(solutionsSlug)(buildEnv); | ||
// TODO: restore this when Strapi will manage guides metadata |
Copilot
AI
Oct 8, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The TODO comment refers to 'guides metadata' but the function getSolutionProps
is handling solutions data, not guides. The comment should be updated to reflect the correct content type.
// TODO: restore this when Strapi will manage guides metadata | |
// TODO: restore this when Strapi will manage solutions metadata |
Copilot uses AI. Check for mistakes.
jsonMetadata?: JsonMetadata | ||
) => { | ||
const strapiReleaseNotes = await fetchReleaseNote(productSlug)(buildEnv); | ||
// TODO: restore this when Strapi will manage guides metadata |
Copilot
AI
Oct 8, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The TODO comment refers to 'guides metadata' but the function getReleaseNoteProps
is handling release notes data, not guides. The comment should be updated to reflect the correct content type.
// TODO: restore this when Strapi will manage guides metadata | |
// TODO: restore this when Strapi will manage release notes metadata |
Copilot uses AI. Check for mistakes.
Depends on: #1696, #1699
List of Changes
Motivation and Context
Manage sync FE with data coming from gitbook avoding to re-deploy
How Has This Been Tested?
Manually on localhost
Screenshots (if appropriate):
Types of changes
Checklist: