Conversation
miakh
force-pushed
the
fix/facebook-feed-current-dom
branch
from
September 2, 2026 20:31
dc90684 to
6ca8b00
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Actions for this post by <author>controlsVerification
npm run buildnpm run typechecknpm run dev -- validate facebook(14 commands, 0 errors/warnings)npm test -- --run clis/facebook/feed.test.js --reporter=dot(22 passed)npm test: 7,320 passed and 4 unrelated tests hit the 5s timeout under the parallel runner; all four affected files passed when rerun individually (88 tests)No account data or captured Facebook markup is included in the fixtures.