Unexpected Behaviour: Empty output in project view cmd

[rizul2108]

The project view command does not give info on the particular project rather outputs an empty table like the one below

rizul@rizu:~/OSS/harbor-cli$ ./harbor-cli project view
┌───────────────────────────────────────────────────────────────────────────────────────┐
│  Project ID  Project Name  Access Level  Type          Repo Count    Creation Time    │
│ ───────────────────────────────────────────────────────────────────────────────────── │
│                                                                                       │
└───────────────────────────────────────────────────────────────────────────────────────┘
rizul@rizu:~/OSS/harbor-cli$ ./harbor-cli project view caoyx
┌───────────────────────────────────────────────────────────────────────────────────────┐
│  Project ID  Project Name  Access Level  Type          Repo Count    Creation Time    │
│ ───────────────────────────────────────────────────────────────────────────────────── │
│                                                                                       │
└───────────────────────────────────────────────────────────────────────────────────────┘

[bupd]

@rizul2108 please try logging in. with harbor-cli login

[rizul2108]

Yeah I tried after logging in only still the table is empty

[bupd]

@rizul2108 try with demo.goharbor.io with username harbor-cli and password as Harbor12345

[rizul2108]

yes i am trying with that only and i found that if i give the output-format flag then the output is correct but if i do not give the output-format it does not give output correctly

harbor-cli/cmd/harbor/root/project/view.go

Line 39 in e23da81

FormatFlag := viper.GetString("output-format")

i am talking about above flag

[rizul2108]

maybe there is some error in formatting the table in viewProjects function i am working on that

[bupd]

Yes, this seems to be a bug.

Thanks

[Standing-Man]

Hi @bupd and @rizul2108, I apologize for forgetting to create an issue earlier. I have addressed this problem in PR #300 I suspect it is caused by an update to the bubbletea.

[rizul2108]

oh yes thank you @Standing-Man