caicloud / nirvana / 499

46%

push

travis-ci

feat(examples): start with config.Command instead of nirvana.Server (#168)

Automatic merge from submit-queue.

feat(examples): start with config.Command instead of nirvana.Server

**What this PR does / why we need it**:

- feat(examples): start with config.Command instead of nirvana.Server

**Which issue(s) this PR fixes** *(optional, close the issue(s) when PR gets merged)*:

Fixes #163 

**Special notes for your reviewer**:

/assign @ddysher 

**Release note**:


```release-note
NONE
```

<!--  Thanks for sending a pull request! Here are some tips:

1. https://github.com/caicloud/engineering/blob/master/docs/review_conventions.md  <-- what is the review process looks like
2. https://github.com/caicloud/engineering/blob/master/docs/commit_conventions.md  <-- how to structure your git commit
3. https://github.com/caicloud/engineering/blob/master/docs/caicloud_bot.md        <-- how to work with caicloud bot

Other tips from Kubernetes cmomunity:

1. If this is your first time, read our contributor guidelines https://git.k8s.io/community/contributors/devel/pull-requests.md#the-pr-submit-process and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
2. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/devel/pull-requests.md#best-practices-for-faster-reviews
3. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/devel/pull-requests.md#write-release-notes-if-needed
4. If the PR is unfinished, see how to mark it: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#marking-unfinished-pull-requests
-->

40 of 40 new or added lines in 11 files covered. (100.0%)

2623 of 4586 relevant lines covered (57.2%)

53.79 hits per line