Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Updating kubemci list to use kubectl tab writer printer #114

Merged
merged 1 commit into from
Jan 12, 2018

Conversation

nikhiljindal
Copy link
Contributor

Fixes #106

Updating formatLoadBalancersList to use kubectl's tab writer printer.

cc @G-Harmon @csbell @madhusudancs

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 15612af on nikhiljindal:printList into ** on GoogleCloudPlatform:master**.

Copy link
Contributor

@G-Harmon G-Harmon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice!

LoadBalancerName: "lb",
},
},
"NAME IP CLUSTERS\nlb \n",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would this be easier to encode with "\t" instead of literal tabs?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I wonder the same. It might be more readable to use \t

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The spacing is not the same in every case and its not always "\t". Depends on the length of value. It gets confusing with lots of /t's and spaces.

Copy link
Contributor

@madhusudancs madhusudancs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor nit. LGTM otherwise.

LoadBalancerName: "lb",
},
},
"NAME IP CLUSTERS\nlb \n",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I wonder the same. It might be more readable to use \t

@nikhiljindal nikhiljindal merged commit 24846a9 into GoogleCloudPlatform:master Jan 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants