-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add tool for filtering FE data in realtime. #318
Conversation
int_val = int(pattern) | ||
result.add(MessageType(int_val)) | ||
# Allow specifying unknown MessageType values if they are preceded by 'u'. | ||
if len(pattern) > 1 and pattern[0] == 'u': |
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.
Is this u prefix really necessary? Any reason not to just treat any manually specified integer as "might be unknown and that's allowable"?
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.
The thought was that 99% of the time an external customer would want to filter known messages and this would allow detecting typos. Other then that just assuming unknown is fine. Maybe the compromise would be to print a warning.
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.
I think in practice this will just be an annoyance more than helpful. The majority of the time someone using this tool is probably going to be specifying message types by name, not number.
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, just some minor cleanup for clarity.
New Features
MessageTypes
to be specified as argsFixes
fast_indexer
results