I've been working on a Go API for Blizzard games data - Opinions appreciated

blov · · 391 次点击    
这是一个分享于 的资源,其中的信息可能已经有所发展或是发生改变。
<p>Hey everyone. I&#39;ve been working on a client library to easily convert Blizzard game API calls into Go structures. I&#39;m looking for help with package structure, ease of use as an API, and any best practices I may have missed.</p> <p>My client library can be viewed here on <a href="https://github.com/FuzzyStatic/blizzard" rel="nofollow">Github</a>. I still have a lot of calls to go!</p> <p>Thank you ahead of time for your feedback!</p> <p>EDIT: Update terminology to better fit my project.</p> <hr/>**评论:**<br/><br/>BadlyCamouflagedKiwi: <pre><p>A small suggestion for your examples; use the := operator more. Instead of </p> <pre><code>var ( seasonRift *SeasonRift err error ) seasonRift, err = d.GetCurrentSeasonNecromancerRift(true) if err != nil { fmt.Println(err) } </code></pre> <p>you can write it more succintly as</p> <pre><code>seasonRift, err := d.GetCurrentSeasonNecromancerRift(true) if err != nil { fmt.Println(err) } </code></pre> <p>which puts more emphasis on your library (the interesting part!) and is less repetitive.</p></pre>FuzzyStatic: <pre><p>Done! Thank you for the suggestions! It definitely makes more sense to show the good stuff and avoid the fluff.</p></pre>neoasterisk: <pre><p>I am confused. Is this an API or a client library for the Blizzard API?</p></pre>FuzzyStatic: <pre><p>After looking up both terminologies, I would say this is a client library for the Blizzard API. I will update the documentation accordingly. TY!</p></pre>

入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889

391 次点击  
加入收藏 微博
0 回复
暂无回复
添加一条新回复 (您需要 登录 后才能回复 没有账号 ?)
  • 请尽量让自己的回复能够对别人有帮助
  • 支持 Markdown 格式, **粗体**、~~删除线~~、`单行代码`
  • 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
  • 图片支持拖拽、截图粘贴等方式上传