-
Notifications
You must be signed in to change notification settings - Fork 29
feat: export pop command #262
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
Conversation
Lazar955
left a comment
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.
utack and lgtm!
gitferry
left a comment
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.
One major concern I have is that we should support user to run this command without db which stores the pk and keyname mapping. In this case, the user should be able to sign pop by keyname
he can use either the key name or eots-pk |
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.
he can use either the key name or eots-pk
Ah I see. I thought loading the db is necessary. Lgtm then. Think we should test this case then somehow. And how do we test it with the api?
…ture instead of the PoP
…to rafilx/export-pop
.golangci.yml
Outdated
| - nlreturn | ||
| - noctx | ||
| - nonamedreturns | ||
| # - nonamedreturns named returns are good |
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.
hm, would disagree with this
#262 New release v0.4.1 after this is merged
No description provided.