Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@jszwedko
Copy link
Contributor

Instead use deprecation pattern described in
https://blog.golang.org/godoc-documenting-go-code.

This will reduce the chances that the application developer will notice that
the deprecations, but I can see the argument that @alienscience is making in
#507 that the current approach is actually an API breakage rather than
a deprecation since the warnings are printed at runtume. More practically, this
has a chance to create a poor user experience for users of applications that
use cli if the application developer doesn't notice the warnings.

Fixes #507

@jszwedko
Copy link
Contributor Author

If we like this, I can backport it the released versions since 1.15.0.

@meatballhat meatballhat added the kind/feature describes a code enhancement / feature request label Aug 22, 2016
@alienscience
Copy link

Thanks, that works much better for me now.

I had problems updating with both Gin (the web server) and CLI last weekend. However, despite two grumpy bug reports both projects have responded politely and fast. My apologies for the tone of my bug report and many thanks for providing CLI.

@meatballhat meatballhat merged commit 05fe449 into master Aug 23, 2016
@meatballhat meatballhat deleted the remove-end-user-deprecation-warnings branch August 23, 2016 15:25
@meatballhat
Copy link
Member

🎷 🐻

@jszwedko
Copy link
Contributor Author

No worries, thank you too, @alienscience

jszwedko added a commit that referenced this pull request Aug 29, 2016
jszwedko added a commit that referenced this pull request Aug 29, 2016
jszwedko added a commit that referenced this pull request Aug 29, 2016
jszwedko added a commit that referenced this pull request Nov 12, 2016
jszwedko added a commit that referenced this pull request Nov 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/feature describes a code enhancement / feature request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants