Skip to content

refactor(apollo-forest-run): cleanup + changes necessary for future fragment watching #575

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 12 commits into from
Jun 23, 2025

Conversation

vladar
Copy link
Contributor

@vladar vladar commented Jun 20, 2025

Various refactors which shouldn't have significant effect on any behavior:

  • cleanup possibleSelection test
  • do not depend on lodash
  • collect all write and modify details in transaction

@vladar vladar changed the title refactor(apollo-forest-run): multiple refactors refactor(apollo-forest-run): refactors necessary for future fragment watching Jun 20, 2025
@vladar vladar changed the title refactor(apollo-forest-run): refactors necessary for future fragment watching refactor(apollo-forest-run): cleanup + changes necessary for future fragment watching Jun 21, 2025
logUpdateStats(this.env, activeTransaction.writes, watchesToNotify);
logUpdateStats(
this.env,
activeTransaction.changelog.filter(isWrite),
Copy link
Contributor

Choose a reason for hiding this comment

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

question: do we really want to always filter? What about to just pass changelog and only if ff is enabled to filter?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point. Updated in 4f8fb25

@vladar vladar merged commit c18f9c5 into main Jun 23, 2025
2 checks passed
@vladar vladar deleted the vladar/fr-refactor-1 branch June 23, 2025 11:13
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