generated from CodeYourFuture/Module-Template
-
-
Notifications
You must be signed in to change notification settings - Fork 30
Sheffield | 25-SDC-Nov | Sheida Shabankari | Sprint 1 |Hashtag slowing down browser #103
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
Open
sheida-shab
wants to merge
4
commits into
CodeYourFuture:main
Choose a base branch
from
sheida-shab:Feat-fixBug-Hashtag-slowingDownBrowser
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
127504b
Add normalized hashtag handling to prevent infinite API calls
sheida-shab 4fd9692
Add Playwright test to verify infinite hashtag requests stop
sheida-shab 64ea09c
Check that API response is for the current hashtag
sheida-shab 80207bf
Replace fixed timeout with waitForResponse to fix hashtag test
sheida-shab File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| import { test, expect } from "@playwright/test"; | ||
|
|
||
| test("should not make infinite hashtag endpoint requests", async ({ page }) => { | ||
| // ===== ARRANGE | ||
| const requests = []; | ||
| const hashtag = "SwizBiz"; | ||
|
|
||
| page.on("request", (request) => { | ||
| if ( | ||
| request.url().includes(`:3000/hashtag/${hashtag}`) && | ||
| request.resourceType() === "fetch" | ||
| ) { | ||
| requests.push(request); | ||
| } | ||
| }); | ||
| // ====== ACT | ||
| // When I navigate to the hashtag | ||
| await page.goto(`/#/hashtag/${hashtag}`); | ||
|
|
||
| // Wait for the hashtag API to respond before continuing | ||
| await page.waitForResponse( | ||
| (response) => | ||
| response.url().includes(`/hashtag/${hashtag}`) && | ||
| response.status() === 200, | ||
| ); | ||
|
|
||
| // ====== ASSERT | ||
| // Then the number of requests should be 1 | ||
| console.log("Number of requests:", requests.length); | ||
| expect(requests.length).toEqual(1); | ||
| }); |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an interesting choice - isn't there a problem here that we may show the title for the new hashtag but the content for the new hashtag, if we render again before the API request finishes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the feedback — I understand the concern about showing the title for a new hashtag while the content might be from a previous hashtag if the API response hasn't returned yet.
To handle this, the code now checks that the hashtag in state is still current before using the API response, so old data is ignored and the view remains consistent.