Skip to content

Conversation

@MarcoPonchia
Copy link
Collaborator

List of Changes

  • Generate synced solution and synced solution list pages
  • Generate synced release-notes

Motivation and Context

Manage sync FE with data coming from gitbook avoding to re-deploy

How Has This Been Tested?

Manually

Screenshots (if appropriate):

Types of changes

  • Chore (nothing changes by a user perspective)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@MarcoPonchia MarcoPonchia self-assigned this Sep 17, 2025
@changeset-bot
Copy link

changeset-bot bot commented Sep 17, 2025

🦋 Changeset detected

Latest commit: d580ab1

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

This PR includes changesets to release 1 package
Name Type
gitbook-docs Minor

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

);
strapiReleaseNotes = data;
strapiReleaseNotes = result.data;
responseJson = result;
Copy link
Collaborator

Choose a reason for hiding this comment

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

fetchFromStrapi output is Promise<{ data: T[]; responseJson?: any }>, why don't you use result.responseJson?

@github-actions
Copy link
Contributor

github-actions bot commented Sep 18, 2025

Jira Pull Request Link

This Pull Request refers to the following Jira issue DEV-2818

@marcobottaro marcobottaro merged commit 8e23e7f into main Sep 18, 2025
12 checks passed
@marcobottaro marcobottaro deleted the DEV-2818-update-script-to-generate-synced-data-in-s3 branch September 18, 2025 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants