Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(isr): use modifyGeneratedHtml in all cache generation process #1760

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

Merged
merged 8 commits into from
Aug 31, 2024

Conversation

maxisam
Copy link
Contributor

@maxisam maxisam commented Aug 29, 2024

fix: #1742 #1758

  • move modifyGeneratedHtml to ISRHandlerConfig
  • consolidate cache generation related code
  • serve existing cache first instead of waiting regeneration
  • create example to show modifyGeneratedHtml in demo

Feel free to make any suggestion. Thanks!

@github-actions github-actions bot added πŸ“š Docs Web Documentation hosted on github pages πŸš€ ISR labels Aug 29, 2024
Copy link

nx-cloud bot commented Aug 29, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 02506d1. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

πŸ“‚ See all runs for this CI Pipeline Execution


πŸŸ₯ Failed Commands
nx affected -t build --exclude=docs --parallel=3
βœ… Successfully ran 6 targets

Sent with πŸ’Œ from NxCloud.

@maxisam
Copy link
Contributor Author

maxisam commented Aug 29, 2024

Trying my best to remove unrelated changes but the lint just keep adding "," back. I hope it is not too hard to review with those changes.

@maxisam maxisam changed the title fix(isr): should use modifyGeneratedHtml in all cache generation process fix(isr): use modifyGeneratedHtml in all cache generation process Aug 29, 2024
Copy link
Member

@eneajaho eneajaho left a comment

Choose a reason for hiding this comment

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

This cleanup was really needed! Thank you!! Amazing job!

@eneajaho
Copy link
Member

@maxisam
A rebase is needed. Then we can merge πŸŽ‰

@maxisam
Copy link
Contributor Author

maxisam commented Aug 29, 2024

@maxisam A rebase is needed. Then we can merge πŸŽ‰

Do you mean you prefer to rewrite some commits and force push it? I usually don't do that since I use squash merge in general.

However, if you prefer to keep some meaningful commits, I can rebase it and force push

@hoebbelsB
Copy link
Member

we are generating the changelog from the commit messages. In best case they are meaningful and we don't have to squash. However, it's also possible. If we can fit your efforts into one meaningful commit message, it should also be fine. Wdyt @eneajaho ?

@eneajaho eneajaho force-pushed the feat/callback-cachemsg branch from 1c7c138 to 4bf27c0 Compare August 31, 2024 17:00
@eneajaho eneajaho force-pushed the feat/callback-cachemsg branch from 4bf27c0 to 10cf6c6 Compare August 31, 2024 17:46
@eneajaho eneajaho force-pushed the feat/callback-cachemsg branch from 10cf6c6 to 02506d1 Compare August 31, 2024 18:02
@eneajaho eneajaho merged commit e59ffb5 into rx-angular:main Aug 31, 2024
10 of 11 checks passed
@eneajaho
Copy link
Member

This PR was breaking, so I will merge this other one too (#1766) so we can release these new features in a minor instead of having to release a major version.

Basically the devs can configure the modify fn in two places and in the next major we can remove the one in the render config.

@maxisam maxisam deleted the feat/callback-cachemsg branch September 3, 2024 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
πŸ“š Docs Web Documentation hosted on github pages πŸš€ ISR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ISR: Invalidating cache does not allow to modify
3 participants