v0.1.3

README.md

@@ -40,10 +40,11 @@ protoc \
 
 Check in `src/option.ts`.
 
-| key               | value          |                                                                                  |
-| ----------------- | -------------- | -------------------------------------------------------------------------------- |
-| useJsonName       | `true`/`false` | `json_name` in a proto file would be used.                                       |
-| enumValueAsString | `true`/`false` | Enum value would be same as member names instead of numbers, which starts with 0 |
+| key                  | value          |                                                                                  |
+| -------------------- | -------------- | -------------------------------------------------------------------------------- |
+| useJsonName          | `true`/`false` | `json_name` in a proto file would be used.                                       |
+| enumValueAsString    | `true`/`false` | Enum value would be same as member names instead of numbers, which starts with 0 |
+| useTypeGuardForOneOf | `true`/`false` | If true, add `type guard functions` for oneof operation, or optional properties. |
 
 ## The mapping rules of proto to TypeScript types
 

ci/release.sh

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+
+SOURCE_DIR=$(cd $(dirname ${BASH_SOURCE:-$0}) && pwd)
+
+cd ${SOURCE_DIR}
+
+new_tag=$(. tag/bump_version.sh)
+git tag -a ${new_tag} -m "${new_tag}"
+
+package_json="../package.json"
+new_tag_without_v=$(echo ${new_tag} | sed s/v//)
+(rm ${package_json} && jq ".version|=\"${new_tag_without_v}\"" > ${package_json}) < ${package_json}

package.json

@@ -1,6 +1,6 @@
 {
   "name": "proto-to-ts-type",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "proto-to-ts-type",
   "author": "yoshinari-yamanaka",
   "license": "MIT",