-
Notifications
You must be signed in to change notification settings - Fork 667
Fix bug pipeline details page for Pipeline with no tasks throws error #2724
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
Fix bug pipeline details page for Pipeline with no tasks throws error #2724
Conversation
|
@vikram-raj I think we probably want to drop that grey circle under the Overview header. I think we probably want to explain why it doesn't have an overview, so maybe something like: Will need UX for the verbiage (cc @serenamarie125 ) I am leaning towards thinking we should keep the title so there isn't just a void in "why don't I see the visualization on this pipeline?" kind of questions. Thoughts Serena? |
|
@andrewballantyne Agree, and there is a separate issue for that and we need confirmation from the issue. Once UX will confirm it then I will remove that. |
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.
pipeline.spec nor pipeline.spec.tasks are guaranteed by the type. Recommend handling the possible NPEs as well.
Also, could we get an explicit type on this variable - like type the FC?
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.
In frontend/public/module/k8s/index.ts, this type is used for other components that this component calls.
export type K8sResourceKind = {
apiVersion?: string;
kind?: string;
metadata?: ObjectMetadata;
spec?: {
selector?: Selector;
[key: string]: any
};
status?: {[key: string]: any};
type?: {[key: string]: any};
data?: {[key: string]: any};
};
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.
@andrewballantyne Done.
54fe537 to
288d7ad
Compare
|
Well, since the design stuff is tracked in another ticket - I'll just review the problem at hand... and that was a NPE breaking things. You fixed that, so I guess that's pretty much it for this PR. /lgtm |
|
@andrewballantyne Yeah, we get the input from the UX then I will fix the design issue as well. |
|
/assign @christianvogt |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewballantyne, christianvogt, vikram-raj The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |

Fix bug - https://jira.coreos.com/browse/ODC-1858