現状Stringで 'true', 'false' じゃないと値が不正と怒られる。
Booleanのtrueが来たらStringに変換する。

前のバージョンリリースしたのが相当前なのでいざこざでおそらくexpireされてるはず。

再度生成してauto deployできるようにしておく。

It’s been a while since last release. Current token maybe expired for the past npm incident.
It must be regenerated.

デコレータでこんな感じに書きたい。

@BaseURI('https://api.annict.com')
class Annict {

    @Endpoint('/v1/me/records/:id')
    update(...) {
    ...
    }

}

悲しみのtslint

https://github.com/domenic/sinon-chai

webpack.config.jsで定義してるBROWSER定数を

if (BROWSER) {
  ...
}

として分岐してるのがまずい。

if (typeof BROWSER !== 'undefined') {
  ...
}

で解決できそう。
あと、環境ごとの分岐テスト書いた方が良さげ。

    it('client works on Node environment', done => {
        expect(typeof BROWSER).to.eql('undefined');
        done();
    });

ブラウザ対応する
#23

#25 (comment)

Annictの仕様なのでannictリポジトリにissueを立てる。
対応されたら #25 をマージしてv0.0.4リリース。
なんらかの理由で返答が対応不可ならブラウザサポートを切ってv0.0.4マイルストーンをclose。

nukosuke/AnnictApp#44

fetch-everywhereに変更するか、もういっそ自分で読み込みの切り替えを実装する。

v0.0.3からTypeScript対応するぞい！

annict.client.setToken("<ANNICT_TOKEN>");

equivalent to

const token = "<ANNICT_TOKEN>";
annict.client.setHeader("Authorization", "Bearer `${token}`");

TypeScriptで

export default class Annict {
   ...
}

とするとjsでrequireは下のようになる。

const Annict = require('annict').default; //<=これがダサい

• mocha
• chai
• nock
• travis

のコンボで

TODO

• /oauth/
• /v1/works
• /v1/episodes
• /v1/records
• /v1/me/statuses
• /v1/me/records
• /v1/me/works
• /v1/me/programs

Annictが英語対応するときいて
see #70

d.tsのPR

because npm v5 supports lock file

currently: it has to be nofified by response error
change to: validate arg Object before sending request

I want mini validation library.

FMI: nukosuke/hubot-annict#3

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

by using TypeDoc

いい加減対応しとく。
ついでに #84 のfailもなおす。

Support TypeScript 3.x and fix CI failure of #84.

Probably, few people use bower now. It is not necessary to support any more.

テストのために入れたが、TS以外のプロジェクトでもtypingsを要求されるので

https://t.co/xeKTYHjd8u #75

new endpoints

• /v1/activities
• /v1/following
• /v1/followers
• /v1/users
• /v1/me
• /v1/me/following_activities

new fields

• record_comments_count (/v1/episodes)
• avatar_url, background_image_url (/v1/users)
• status.kind (/v1/me/works)
• filter_has_record_comment (/v1/records)

npm WARN deprecated @types/[email protected]: This is a stub types definition for es6-promise (https://github.com/jakearchibald/ES6-Promise). es6-promise provides its own type definitions, so you don't need @types/es6-promise installed!

remove @types/es6-promise from package.json

• Promise<IResponse>
• Promise<Works>

とか現状バラバラ