-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat(lineage): show fully qualified task name in lineage UI #6126
feat(lineage): show fully qualified task name in lineage UI #6126
Conversation
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! I have a suggestion but not blocking from me approving
@@ -22,6 +22,24 @@ const getDataJobPlatformName = (data?: DataJob): string => { | |||
return data?.dataFlow?.platform?.properties?.displayName || data?.dataFlow?.platform?.name || ''; | |||
}; | |||
|
|||
const getExpandedNameForDataJob = (entity: DataJob): string => { | |||
const name = entity?.properties?.name; |
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.
what do you think about doing const name = new DataJobEntity().displayName(entity);
in order to keep getting display names for dataJobs consistent?
@@ -178,6 +196,7 @@ export class DataJobEntity implements Entity<DataJob> { | |||
return { | |||
urn: entity?.urn, | |||
name: entity?.properties?.name || '', |
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.
and if we're gonna be consistent about using displayName
we could also update this here to be name: this.displayName(entity),
Allows option to see full name of a task (data flow . task) in lineage viz.
Checklist