Merge pull request #116 from GameBridgeAI/deno_build_update

v1.2.1-rc

Author: Scott Hardy

.github/workflows/scripts/build.sh

@@ -12,10 +12,6 @@ fi
 
 .github/workflows/scripts/npm_release_files/create_npm_package_file_test.sh
 
-curl -L https://deno.land/x/install/install.sh | sh -s "v1.6.3"
-
-export PATH="$HOME/.deno/bin:$PATH"
-
 mkdir dist
 
 deno run -r --unstable --allow-read --allow-run --no-check ./.github/workflows/scripts/npm_release_files/babel_ts_serialize.ts > dist/ts_serialize.js
@@ -36,6 +32,7 @@ cd dist
 cd ../examples/node
 
 npm ci
+
 npm ln ../../dist
 
 npm test

.github/workflows/ts_serialize_release.yml

@@ -12,7 +12,7 @@ jobs:
 
     strategy:
       matrix:
-        deno: ["v1.6.x"]
+        deno: ["v1.x"]
         os: [macOS-latest, windows-latest, ubuntu-latest]
 
     steps:
@@ -44,7 +44,7 @@ jobs:
 
     strategy:
       matrix:
-        deno: ["v1.6.x"]
+        deno: ["v1.x"]
 
     steps:
       - name: Get github tag

.github/workflows/ts_serialize_tests.yml

@@ -17,7 +17,7 @@ jobs:
 
     strategy:
       matrix:
-        deno: ["v1.6.x"]
+        deno: ["v1.x"]
         os: [macOS-latest, windows-latest, ubuntu-latest]
 
     steps:

CHANGELOG.md

@@ -12,6 +12,10 @@ and this project adheres to
 
 - missing copyright statement
 - basic benchmark tests
+- update deno@1.7.1, std@0.85.0
+- change builds to use v1.x
+- removed deno install from build script
+- deno fmt with new rules
 
 ## [v1.2.0] - 2021-01-22
 
@@ -34,7 +38,8 @@ and this project adheres to
 ### Added
 
 - docs for @SerializeProperty short cut functions
-- new `strategy/utils.ts` exposing `getNewSerializable(type)` for custom decorators
+- new `strategy/utils.ts` exposing `getNewSerializable(type)` for custom
+  decorators
 - fixes #100
 - fixes #105
 - fixes #99

benchmarks/README.md

@@ -1,3 +1,3 @@
 # Benchmarks
 
-To run use `$ deno test -- --benchmark`
+To run use `$ deno test -- --benchmark`

docs/serializable.md

@@ -209,12 +209,12 @@ assertEquals(
 ## Short cutting the `@SerializeProperty` decorator
 
 While `@SerializeProperty` is handy with to and from JSON strategies, it can
-still be verbose to declare the strategies for each property. You can define your 
-owndecorator functions to wrap `@SerializeProperty` and provide the `toJSONStrategy`
-and `fromJSONStrategy`. An example short cut is providing a `type` to use with
-`toSerializable`. `SerializableConstructor` and `getNewSerializable` are provided 
-to allow a raw serializable type or a function that returns a constructed serializable 
-type enabling constructor arguments: 
+still be verbose to declare the strategies for each property. You can define
+your owndecorator functions to wrap `@SerializeProperty` and provide the
+`toJSONStrategy` and `fromJSONStrategy`. An example short cut is providing a
+`type` to use with `toSerializable`. `SerializableConstructor` and
+`getNewSerializable` are provided to allow a raw serializable type or a function
+that returns a constructed serializable type enabling constructor arguments:
 
 ```ts
 export function DeserializeAs<T>(

examples/deno/deps.ts

@@ -10,4 +10,4 @@ export {
   toSerializable,
   TransformKey,
 } from "https://deno.land/x/ts_serialize/mod.ts";
-export { readJson } from "https://deno.land/std@0.84.0/fs/mod.ts";
+export { readJson } from "https://deno.land/std@0.85.0/fs/mod.ts";

test_deps.ts

@@ -7,4 +7,4 @@ export {
   assertEquals,
   assertStrictEquals,
   fail,
-} from "https://deno.land/std@0.84.0/testing/asserts.ts";
+} from "https://deno.land/std@0.85.0/testing/asserts.ts";