Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

v2 changes #12

Merged
merged 12 commits into from
Jan 4, 2023
Merged

v2 changes #12

merged 12 commits into from
Jan 4, 2023

Conversation

xen0n
Copy link
Collaborator

@xen0n xen0n commented Jan 3, 2023

No description provided.

@xen0n xen0n force-pushed the no-forced-init branch 2 times, most recently from df9793b to 3737151 Compare January 4, 2023 02:39
@xen0n xen0n mentioned this pull request Jan 4, 2023
xen0n added 11 commits January 4, 2023 13:33
…effect out of main package

This is hidden magic, and can subtly change CLI semantics if unknowingly
incorporated into an existing codebase (e.g. simple commands with usages
like `foo <input file>` will suddenly stop processing the path `version`).

Move the init side-effect to separate package so at least this aspect is
opt-in.
Otherwise you may assume it's a getter of some versioning structure,
while in fact it's just a bunch of printf's.
It doesn't control the main package.
The "N/A" string constant is not exported so it serves little purpose,
and not being the zero value it can confuse users used to the typical Go
idiom of representing unknown quantities with zero values.
@CarlJi CarlJi merged commit b98b130 into qiniu:main Jan 4, 2023
@xen0n xen0n deleted the no-forced-init branch January 4, 2023 06:14
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants