-
Notifications
You must be signed in to change notification settings - Fork 187
[superlog] Skip unsupported filter fields per query type instead of throwing #477
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
superlog-app
wants to merge
1
commit into
staging
Choose a base branch
from
superlog/skip-unsupported-batch-filters
base: staging
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.
+44
−9
Open
Changes from all commits
Commits
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
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
Oops, something went wrong.
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.
Set.prototype.includesdoes not exist — TypeError on every request with filtersGLOBAL_ALLOWED_FILTERSis declared asnew Set([...])(line 44).Sethas.has(), not.includes(). Calling.includes()on aSetthrowsTypeError: GLOBAL_ALLOWED_FILTERS.includes is not a functionat runtime, which would crash every query that carries filters — a regression worse than the original throw. The pre-existingisFilterFieldAllowedhelper (line 61-68) already performs this exact check correctly using.has(). The entire new block should be replaced with a single call to that helper:The type assertion
as (typeof GLOBAL_ALLOWED_FILTERS)[number]is also unsound for aSet—Set<string>[number]resolves toundefined— but it is superseded by the runtime crash anyway.