Corrected a filter preparation logic for tables on API types pages#414
Merged
Corrected a filter preparation logic for tables on API types pages#414
Conversation
DF v7.1.0 with event scripts fixes for Py3 and Snowflake keypair auth
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I found an odd behaviour for the search component on the tabs under api types. Due to how the filter parameter is being built on the front-end request can return services that are not related to the opened page. Here is a short GIF example of how it works:
I was able to resolve it by simply wrapping some part of the filter in parentheses, and removing created_by id is not null