-
Notifications
You must be signed in to change notification settings - Fork 11
Explorer subpath support #1368
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
Merged
Merged
Explorer subpath support #1368
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
5ad6e85
feat: add support for attribute expressions
aaron-steinfeld 60a6bcd
Merge remote-tracking branch 'origin/main' into attribute-expressions
aaron-steinfeld 775d4aa
test: update tests
aaron-steinfeld 46648ea
Merge branch 'main' into attribute-expressions
aaron-steinfeld a7efe69
feat: add support for filtering with attribute expressions
aaron-steinfeld bb7ba1a
fix: caught a couple bugs while updating tests
aaron-steinfeld 2751bcd
Merge remote-tracking branch 'origin/main' into explorer-subpath-support
aaron-steinfeld 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
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
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.
How are tooltips now handled? Or at least, how do we let users know the underlying field backing the display name?
Uh oh!
There was an error while loading. Please reload this page.
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 actually removed them, this was one of the things I wanted to ask. In the existing UI:
Example from existing ui:


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.
Fair points. Knowing the underlying keys was an ask early on, so we've always had the tooltip available. Not sure if users are even asking for that info. If they are, I'm surprised we haven't gotten feedback about the discoverability of it as you've noted.
I'm fine removing them as long as its a quick fix to add back if an issue arrises.
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.
Yeah I remember the ask, but not sure why it was there given that we don't expose keys to users anywhere else. Easy enough to restore if the requirement comes back - hopefully can better understand the ask at that point.