-
-
Notifications
You must be signed in to change notification settings - Fork 71
Default filter user checks (issue #1082) #1120
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
Conversation
Taeir
left a comment
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 fixing this issue :) I left a few questions and minor remarks. Please note that JavaScript is not the language I know the best so my apologies if those questions or remarks are not possible or required.
…JSDoc to make the intent clearer
…turning raw response if there is a pending request
Taeir
left a comment
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.
Looks good with the latest changes!
This PR addresses issues raised in #1082, in particular — the problem with the client-side JavaScript attempting to fetch default filter for users that are not signed in. CircleCI (rubocop) is expected to fail until #1019 is merged in develop.
Regarding the addition of
_pendingUser- it exists to prevent additional calls to/users/meas I noticed there can be up to 5 made because theQPixel#usermethod doesn't account for other requests in flight. I could use abort signals, but this solution allows us not to send redundant requests in the first place.