Skip to content
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

Render legacy only pages #2733

Merged
merged 12 commits into from
Mar 10, 2025
Merged

Render legacy only pages #2733

merged 12 commits into from
Mar 10, 2025

Conversation

arnaucasau
Copy link
Collaborator

@arnaucasau arnaucasau commented Mar 6, 2025

Closes #2685

This PR extends the page render checker to verify the legacy only pages. When the new --legacy argument is used, the checker will only run for non-API pages that are not cloud only.

Tests

  • In c43afa4 I changed 1 common page and 1 legacy only page. This results in the checker verifying 1 page when running in cloud mode and 2 pages when running in legacy mode
  • In 6c205b6 2 extra cloud only pages. This results in the checker verifying 3 page when running in cloud mode and 2 pages when running in legacy mode
  • In e599a5e I converted a legacy page to cloud only to make CI fail.

if: steps.all-changed-files.outputs.any_changed == 'true'
run: |
npm run check:pages-render -- --from-file .github/outputs/all_changed_files.txt
- name: Stop Docker preview (cloud app)
if: steps.all-changed-files.outputs.any_changed == 'true'
run: docker ps -q | xargs docker stop
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This is necessary to avoid trying to run two web servers in the same port when checking the legacy app

@arnaucasau arnaucasau changed the title [WIP] Render legacy only pages Render legacy only pages Mar 6, 2025
@arnaucasau arnaucasau marked this pull request as ready for review March 6, 2025 12:41
Copy link
Collaborator

@Eric-Arellano Eric-Arellano left a comment

Choose a reason for hiding this comment

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

Excellent job 👏 Nice attention to detail with how you handle API pages

arnaucasau and others added 2 commits March 10, 2025 10:52

Partially verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
Co-authored-by: Eric Arellano <[email protected]>

Partially verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
Co-authored-by: Eric Arellano <[email protected]>
Copy link
Member

@frankharkins frankharkins left a comment

Choose a reason for hiding this comment

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

Awesome! Very clean implementation

@arnaucasau arnaucasau added this pull request to the merge queue Mar 10, 2025
Merged via the queue into main with commit 5f52141 Mar 10, 2025
3 checks passed
@arnaucasau arnaucasau deleted the AC/render-legacy-app branch March 10, 2025 10:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Decide if we want the pages render check for legacy docs
3 participants