chore(taquito) Rename project from tezos-ts to taquito

Author: carte7000

.circleci/config.yml

@@ -34,18 +34,18 @@ jobs:
       - image: circleci/node:8.11.4
     steps:
       - checkout
-      - run: cd website && npm install && npm run build && cp -R build/tezos-ts ../dist
+      - run: cd website && npm install && npm run build && cp -R build/taquito ../dist
       - run: npm install
       - run: npm run lerna -- bootstrap
       - run: npm run lerna run build
       - run: npm run build-docs
-      - run: cd packages/tezos-ts-react-components && npm run build-storybook -- -o ../../dist/react-storybook
-      - run: cd dist && touch .nojekyll && echo 'tezos-ts.io' > CNAME
+      - run: cd packages/taquito-react-components && npm run build-storybook -- -o ../../dist/react-storybook
+      - run: cd dist && touch .nojekyll && echo 'taquito.tez.ie' > CNAME
       - run:
           command: |
             git config user.email "[email protected]"
             git config user.name "ci-build"
-            npm run gh-pages -- --dist dist --dotfiles --silent --repo https://[email protected]/ecadlabs/tezos-ts.git
+            npm run gh-pages -- --dist dist --dotfiles --silent --repo https://[email protected]/ecadlabs/taquito.git
 workflows:
   version: 2
   test_and_deploy:

README.md

@@ -1,7 +1,7 @@
 # Tezos Typescript Library Suite
 
-[![CircleCI](https://circleci.com/gh/ecadlabs/tezos-ts.svg?style=svg)](https://circleci.com/gh/ecadlabs/tezos-ts)
-[![codecov](https://codecov.io/gh/ecadlabs/tezos-ts/branch/master/graph/badge.svg)](https://codecov.io/gh/ecadlabs/tezos-ts)
+[![CircleCI](https://circleci.com/gh/ecadlabs/taquito.svg?style=svg)](https://circleci.com/gh/ecadlabs/taquito)
+[![codecov](https://codecov.io/gh/ecadlabs/taquito/branch/master/graph/badge.svg)](https://codecov.io/gh/ecadlabs/taquito)
 
 ## Work In Progress / Alpha
 
@@ -17,8 +17,8 @@ The goals of this library are:
 * Nightly and Continuous integration tests against official Tezos RPC nodes
 * dApp development uses cases a first-class concern, empowering new developers to get results quickly
 * No dependencies on the Tezos RPC node for generating operations (Ex: not dependant on “forge” RPC method).
-* Well documented API using [TypeDoc](https://tezos-ts.io/typedoc)
-* Set of ready-made React components for common use-cases, with a [Demo Gallery](https://tezos-ts.io/react-storybook/)
+* Well documented API using [TypeDoc](https://taquito.tez.ie/typedoc)
+* Set of ready-made React components for common use-cases, with a [Demo Gallery](https://taquito.tez.ie/react-storybook/)
 * Regular versioned releases, published to npmjs.org, with a published version strategy
 * Participation in the [CII Best Practices](https://bestpractices.coreinfrastructure.org) program and all requirements entailed therein
 * Portable - This library has minimum dependencies, making it usable in any js project on the front or back end.
@@ -27,48 +27,48 @@ The goals of this library are:
 
 ## Project Organization
 
-`tezos-ts` is organized as a mono repository from which several npm packages are built and published. Packages are in the `packages/` directory, each one with its a README file.
+`taquito` is organized as a mono repository from which several npm packages are built and published. Packages are in the `packages/` directory, each one with its a README file.
 
-We publish gpg signed packages to npmjs.org under the `@tezos-ts` handle.
+We publish gpg signed packages to npmjs.org under the `@taquito` handle.
 
 | Package                                                           |                        Responsibility                         |
 | ----------------------------------------------------------------- | ------------------------------------------------------------- |
-| [@tezos-ts/tezos-ts](packages/tezos-ts)                                     | Regroup every other library and provide higher level utility  |
-| [@tezos-ts/react-components](packages/tezos-ts-react-components)   | React components that implement some common use cases         |
-| [@tezos-ts/rpc](packages/tezos-ts-rpc)                             | RPC client library, wrap every rpc endpoint in its own method |
-| [@tezos-ts/michelson-encoder](packages/tezos-ts-michelson-encoder) | Encode/Decode storage and parameters to/from michelson format |
-| [@tezos-ts/indexer](packages/tezos-ts-indexer)                     | A client for the [tezos-indexer-api][0] API                   |
-| [@tezos-ts/streamer](packages/tezos-ts-streamer)                   | A client for the [tezos-ts-streamer][1] API              |
-| [@tezos-ts/signer](packages/tezos-ts-signer)                   | Provide necessary function to sign using tezos keys  |
-| [@tezos-ts/utils](packages/tezos-ts-utils)                   | Provide different encoding and decoding utilities |
+| [@taquito/taquito](packages/taquito)                                     | Regroup every other library and provide higher level utility  |
+| [@taquito/react-components](packages/taquito-react-components)   | React components that implement some common use cases         |
+| [@taquito/rpc](packages/taquito-rpc)                             | RPC client library, wrap every rpc endpoint in its own method |
+| [@taquito/michelson-encoder](packages/taquito-michelson-encoder) | Encode/Decode storage and parameters to/from michelson format |
+| [@taquito/indexer](packages/taquito-indexer)                     | A client for the [tezos-indexer-api][0] API                   |
+| [@taquito/streamer](packages/taquito-streamer)                   | A client for the [taquito-streamer][1] API              |
+| [@taquito/signer](packages/taquito-signer)                   | Provide necessary function to sign using tezos keys  |
+| [@taquito/utils](packages/taquito-utils)                   | Provide different encoding and decoding utilities |
 
 ## API Documentation
 
-The TypeDoc style API documentation is available [here](https://tezos-ts.io/typedoc)
+The TypeDoc style API documentation is available [here](https://taquito.tez.ie/typedoc)
 
 ### React Components overview
 
 React component demos are published using the [storybook](https://storybook.js.org) tool.
 
-View the demo components here: [Tezos components Storybook](https://tezos-ts.io/react-storybook)
+View the demo components here: [Tezos components Storybook](https://taquito.tez.ie/react-storybook)
 
 ## Versioning Strategy
 
 Version releases use "Semantic Versioning" style version numbers, but deviates from SemVer norms when it comes to the "Major" number.
 
-We use SemVer style versions for tezos-ts, but we make the "Major" version number track against the latest Tezos economical protocol we have tested on.
+We use SemVer style versions for taquito, but we make the "Major" version number track against the latest Tezos economical protocol we have tested on.
 
-For example, in August 2019, the economic protocol was `004-Pt24m4xi`, and `005-PsBABY5H` was (is) working its way through the on-chain amendment process. Therefore the current version number for tezos-ts would be `v4.0.0`. During this time, we would start working on `v5.0.0-beta.1` on the expectation (but not the assumption) that it shall become our new economic protocol.
+For example, in August 2019, the economic protocol was `004-Pt24m4xi`, and `005-PsBABY5H` was (is) working its way through the on-chain amendment process. Therefore the current version number for taquito would be `v4.0.0`. During this time, we would start working on `v5.0.0-beta.1` on the expectation (but not the assumption) that it shall become our new economic protocol.
 
 When we are confident that the next protocol proposal going to be promoted, AND we have implemented and tested interoperability with the new protocol (and potentially node RPC changes) we shall them release `v5.0.0` BEFORE the chain transitions to the new protocol.
 
-It is essential that the packages supporting the new protocol be released before the chain transitions to the new economic protocol so that developers who build on top of tezos-ts have time to update and test their projects.
+It is essential that the packages supporting the new protocol be released before the chain transitions to the new economic protocol so that developers who build on top of taquito have time to update and test their projects.
 
-During "Major" version updates, breaking changes in the tezos-ts public APIs MAY include breaking changes, for which we will make a strong effort to announce and document in our release notes. The Minor and Patch version numbers follow SemVer norms.
+During "Major" version updates, breaking changes in the taquito public APIs MAY include breaking changes, for which we will make a strong effort to announce and document in our release notes. The Minor and Patch version numbers follow SemVer norms.
 
 All releases are backward compatible with chain data back to the genesis block. Support for older Tezos node RPCs is maintained where feasible but will be dropped eventually. Tezos node RPC support also depends on what versioning strategy gets adopted by the canonical Tezos node. At the time of writing, this is unclear.
 
-Supported versions of the tezos-ts packages will be maintained for the current and next protocol versions. Teams using older versions are encouraged to update, but if blockers exist, they are encouraged to contact us.
+Supported versions of the taquito packages will be maintained for the current and next protocol versions. Teams using older versions are encouraged to update, but if blockers exist, they are encouraged to contact us.
 
 ## Releases
 
@@ -113,7 +113,7 @@ Reports may be encrypted using keys published on keybase.io using [keybase/jevon
 
 ### Other Issues & Feature Requests
 
-Please use the [GitHub issue tracker](https://github.com/ecadlabs/tezos-ts/issues) to report bugs or request features.
+Please use the [GitHub issue tracker](https://github.com/ecadlabs/taquito/issues) to report bugs or request features.
 
 ## Contributions
 

docs/inmemory_signer.md

@@ -13,13 +13,13 @@ This signer implementation is meant to be used for development and not for produ
 
 ```js
 
-import { InMemorySigner } from '@tezos-ts/signer'
-import { Tezos } from '@tezos-ts/tezos-ts'
+import { InMemorySigner } from '@taquito/signer'
+import { Tezos } from '@taquito/taquito'
 
 Tezos.setProvider({signer: new InMemorySigner('you_private_key')})
 ```
 
-If you configure tezos-ts this way you will now be able to use every function that needs signing support
+If you configure taquito this way you will now be able to use every function that needs signing support
 
 `Note: Operation will be signed automatically using the signer (no prompt)`
 

docs/quick_start.md

@@ -6,13 +6,13 @@ author: Simon Boissonneault-Robert
 ## Installing the library
 
 ```
-npm run install @tezos-ts/tezos-ts
+npm run install @taquito/taquito
 ```
 
 ## Import the library in your project
 
 ```js
-import { Tezos } from '@tezos-ts/tezos-ts'
+import { Tezos } from '@taquito/taquito'
 ```
 
 ## Configuration
@@ -26,7 +26,7 @@ Tezos.setProvider({rpc: "your_rpc"})
 ### Changing the underlying signer
 
 ```js
-import { TezBridgeSigner } from '@tezos-ts/tezbridge-signer';
+import { TezBridgeSigner } from '@taquito/tezbridge-signer';
 
 Tezos.setProvider({signer: new TezBridgeSigner()})
 ```

docs/tezbridge_signer.md

@@ -8,8 +8,8 @@ author: Simon Boissonneault-Robert
 You first need to include https://www.tezbridge.com/plugin.js in your application to use this signer
 
 ```js
-import { TezBridgeSigner } from '@tezos-ts/tezbridge-signer'
-import { Tezos } from '@tezos-ts/tezos-ts'
+import { TezBridgeSigner } from '@taquito/tezbridge-signer'
+import { Tezos } from '@taquito/taquito'
 
 Tezos.setProvider({signer: new TezBridgeSigner()})
 ```

example/contract-origination.ts

@@ -1,4 +1,4 @@
-import { Tezos } from '@tezos-ts/tezos-ts';
+import { Tezos } from '@taquito/taquito';
 
 const provider = 'https://alphanet-node.tzscan.io';
 

example/contract-schema.ts

@@ -1,5 +1,5 @@
-import { Tezos } from '@tezos-ts/tezos-ts';
-import { InMemorySigner } from '@tezos-ts/signer';
+import { Tezos } from '@taquito/taquito';
+import { InMemorySigner } from '@taquito/signer';
 
 
 async function example() {

example/example-activate.ts

@@ -1,4 +1,4 @@
-import { Tezos } from '@tezos-ts/tezos-ts'
+import { Tezos } from '@taquito/taquito'
 
 
 async function example() {

example/example-node.ts

@@ -1,6 +1,6 @@
-import { Tezos } from '../packages/tezos-ts/src/tezos-ts';
-import { RpcClient } from '../packages/tezos-ts-rpc/src/tezos-ts-rpc';
-import { castToString } from '../packages/tezos-ts-rpc/src/utils/utils';
+import { Tezos } from '../packages/taquito/src/taquito';
+import { RpcClient } from '../packages/taquito-rpc/src/taquito-rpc';
+import { castToString } from '../packages/taquito-rpc/src/utils/utils';
 
 const provider = 'https://alphanet-node.tzscan.io';
 const client = new RpcClient(provider);