UI: Display feature key column in feature table - #569
Merged
xiaoyongzhu merged 3 commits intoAug 11, 2022
Merged
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
Thanks! LGTM |
Sorry, something went wrong.
xiaoyongzhu
previously approved these changes
Aug 10, 2022
Yuqing-cat
approved these changes
Aug 11, 2022
Comment thread
.github/pull_request_template.md
xiaoyongzhu
approved these changes
Aug 11, 2022
ahlag
pushed a commit
to ahlag/feathr
that referenced
this pull request
Aug 26, 2022
* Add key column in feature list page * Fix lint issues * Change Key to Entity Key
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
Reviewers
3 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.
Description
This PR updates UI feature table to display feature key columns.
How was this patch tested?
Verified feature key can be displayed correctly in feature table
Does this PR introduce any user-facing changes?