-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fix/fields #326
Open
chuanlin2018
wants to merge
3
commits into
integration
Choose a base branch
from
fix/fields
base: integration
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
Fix/fields #326
Conversation
This file contains 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
I’ll take a look.
From: shiftmed ***@***.***>
Date: Tuesday, December 17, 2024 at 6:43 PM
To: usnistgov/oar-sdp ***@***.***>
Cc: Lin, Chuan (Assoc) ***@***.***>, Author ***@***.***>
Subject: Re: [usnistgov/oar-sdp] Fix/fields (PR #326)
Hello Chuan,
On the home page, the issue seems to be fixed. Each refresh of the app correctly requests the fields endpoint a single time.
On the search page, it appears to be trickier. On the first search (i.e. home page => type into search box => launch search), it triggers an additional /fields request (which I suppose is working as intended); however if I now refresh that same page with the results already loaded (i.e. "launch" the app from the URL), 3 requests to the fields endpoint are triggered as displayed on the screenshot below.
fields-bug.png (view on web)<https://github.com/user-attachments/assets/8a38f4eb-0a22-49ce-92ae-5f3f3d97e177>
—
Reply to this email directly, view it on GitHub<#326 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKQHD3DZNQEMNT6HADGBAYT2GCZKNAVCNFSM6AAAAABTZDSGPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBZHEYTAMJVGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I think it's fixed this time... |
The fields endpoint now successfully only gets queried once. There is however a new unexpected behavior during filtering:
To replicate:
Thanks @chuanlin2018! |
Ah! I will take a look... |
Thanks @chuanlin2018. I am investigating this; it seems to be a bug on my end related to a mismatch between Angular 18 and PrimeNG. This PR is passing. |
shiftmed
approved these changes
Jan 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi Mehdi, I think I fixed the multiple requests issue. Please verify.
You can either merge it into integration or your fix/unnecessary-core-js branch if you confirm it's fixed.
Thanks.
Chuan