-
Notifications
You must be signed in to change notification settings - Fork 16.7k
fix(fe/dashboard-list): display modifier info for Last modified data
#32035
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
rusackas
merged 5 commits into
apache:master
from
hainenber:fix/missing-modifier-tooltip-in-dashboard-list
Feb 21, 2025
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
f7bd9a6
fix(fe/dashboard-list): display modifier info for `Last modified` data
hainenber add32de
chore: update DashboardList unit test with new fetch query params
hainenber 8f37ad2
Merge branch 'master' into fix/missing-modifier-tooltip-in-dashboard-…
hainenber d7f4a17
chore: re-add dashboard columns with nested field type to avoid break…
hainenber 88fc9e0
fix(ci): refactor unit test to reflect changes in fetched dashboard c…
hainenber 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.
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.
@hainenber Can you confirm that the
owners' fields, apart fromid,first_nameandlast_name, are not being used? Same forchanged_by's fields.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 attributes like
owners.last_nameare the one populating the owners field. For some reasons, you have to specify atributes for nested fields likeownersandchanged_by.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.
Maybe you misunderstood what I mean. Previously, we had
ownersbeing declared which means that ALL attributes ofownerswere accessible likefull_name. Now that you excludedownersfrom the fetched columns, if there's some component accessingfull_name, it will break. I'm ok with removing the whole owners object but we need to check which attributes are in fact being used so that the projection is correct.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 see. Then in that case, I'll only add the missing attributes and not to remove the nested field names to minimize any risks.
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.
Re-added old nested fields. Issue is still fixed with less risks :D