dcl-catalyst-client 15.0.0 → 17.0.0

package/.eslintignore

@@ -2,4 +2,5 @@ dist
 jest.config.js
 scripts
 coverage
-src/CatalystsList.ts
+src/contracts-snapshots/data.ts
+docs

package/.github/workflows/build-and-publish.yml

@@ -1,3 +1,5 @@
+name: build and publish
+
 on:
   push:
     branches:
@@ -7,78 +9,15 @@ on:
     types:
       - created
 
-name: build-deploy
-jobs:
-  check_and_build:
-    runs-on: ubuntu-latest
-    outputs:
-      s3_bucket_key: ${{ steps.publish_package.outputs.s3-bucket-key }}
-    steps:
-      - uses: actions/checkout@v2
-      - name: install
-        run: yarn install --frozen-lockfile
-      - name: build
-        run: yarn build
-      - name: test
-        run: yarn test
-      - name: validate
-        run: yarn lint:check
-      - name: publish packages
-        uses: menduz/oddish-action@master
-        id: publish_package
-        with:
-          registry-url: 'https://registry.npmjs.org'
-          access: public
-          ## use action runId instead of current date to generate snapshot numbers
-          deterministic-snapshot: true
-
-          ## publish every package to s3
-          s3-bucket: ${{ secrets.SDK_TEAM_S3_BUCKET }}
-          s3-bucket-key-prefix: '@dcl/${{ github.event.repository_name }}/branch/${{ steps.myref.outputs.branch }}'
-
-          ## inform gitlab after publishing to proceed with CDN propagation
-          gitlab-token: ${{ secrets.GITLAB_TOKEN }}
-          gitlab-pipeline-url: ${{ secrets.GITLAB_URL }}
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-          AWS_DEFAULT_REGION: us-east-1
-          AWS_ACCESS_KEY_ID: ${{ secrets.SDK_TEAM_AWS_ID }}
-          AWS_SECRET_ACCESS_KEY: ${{ secrets.SDK_TEAM_AWS_SECRET }}
 
-  notify_deployment:
-    needs: [check_and_build]
-    if: ${{ github.event.pull_request.number }}
-    runs-on: ubuntu-latest
-    name: Deployment Notification
-    steps:
-      - name: Find Comment
-        uses: peter-evans/find-comment@v1
-        id: fc
-        with:
-          issue-number: ${{ github.event.pull_request.number }}
-          comment-author: 'github-actions[bot]'
-          body-includes: Test this pull request
-
-      - name: Get the current branch name
-        shell: bash
-        run: node -e "console.log('::set-output name=branch::' +    ('${{github.head_ref}}' || '$GITHUB_REF'.replace('refs/heads/',''))    )"
-        id: myref
-
-      - name: Generate S3 URL
-        id: url-generator
-        run: |
-          body=$(echo ${{ secrets.SDK_TEAM_S3_BASE_URL }})/${{ needs.check_and_build.outputs.s3_bucket_key }}
-          echo ::set-output name=body::$body
-
-      - name: Create or update comment
-        uses: peter-evans/create-or-update-comment@v1
-        with:
-          comment-id: ${{ steps.fc.outputs.comment-id }}
-          issue-number: ${{ github.event.pull_request.number }}
-          body: |
-            # Test this pull request
-            - The package can be tested by running
-               ```bash
-               yarn upgrade "${{ steps.url-generator.outputs.body }}"
-               ```
-          edit-mode: replace
+jobs:
+  build-publish:
+    uses: decentraland/platform-actions/.github/workflows/libs-build-and-publish.yml@main
+    secrets:
+      SDK_TEAM_S3_BUCKET: ${{ secrets.SDK_TEAM_S3_BUCKET }}
+      GITLAB_TOKEN: ${{ secrets.GITLAB_TOKEN }}
+      GITLAB_URL: ${{ secrets.GITLAB_URL }}
+      NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+      SDK_TEAM_AWS_ID: ${{ secrets.SDK_TEAM_AWS_ID }}
+      SDK_TEAM_AWS_SECRET: ${{ secrets.SDK_TEAM_AWS_SECRET }}
+      SDK_TEAM_S3_BASE_URL: ${{ secrets.SDK_TEAM_S3_BASE_URL }}

package/README.md

@@ -8,66 +8,72 @@ Welcome to the Catalyst Client library. This client can be used to interact with
 npm install dcl-catalyst-client
 ```
 
-## Usage
+### Implementations
 
-You can check the entire API [here](src/CatalystAPI.ts).
+The examples in this document illustrate the implementation of common workflows using the second version of `catalyst-client`.
 
-This library depends on two other Decentraland libraries:
+#### Connect to random Catalyst
 
-- [Decentraland Crypto](https://github.com/decentraland/decentraland-crypto/)
-- [Catalyst Commons](https://github.com/decentraland/catalyst-commons/)
+The following section outlines the steps to successfully connect to a random catalyst when there is no need to communicate with any particular node.
 
-### Deploying
+```javascript
+import { connectedToRandomCatalyst } from 'dcl-catalyst-client'
+import { getCatalystServersFromCache } from './../dist/contracts-snapshots'
+import { createFetchComponent } from './../dist/client/utils/fetcher'
 
-One of the most important aspects, is the ability to deploy new entities. Here is an example of how to do it:
+// Connect to a catalyst randomly choosen from the catalyst-client snapshot
+const fetcher = createFetchComponent()
+const nodes = getCatalystServersFromCache('mainnet')
+const catalyst = await connectedToRandomCatalyst(nodes, { fetcher })
 
+if (!catalyst) {
+  console.log('No catalyst node is available right now')
+  return
+}
+
+const catalystInfo = await catalyst.fetchAbout()
+const contentClient = await catalyst.getContentClient()
+const lambdasClient = await catalyst.getLambdasClient()
 ```
-import { CatalystClient, DeploymentBuilder } from 'dcl-catalyst-client'
-import { EntityType } from '@dcl/schemas'
-import { Authenticator } from '@dcl/crypto'
 
+#### Deploy an entity
 
-// This is up to you. You will need to figure out how to make the owner of the pointer sign the entity id
-const { signature, address } = await sign(entityId)
+The following section outlines the steps to deploy an entity to the Decentraland network.
 
-// You can then create a simple auth chain like this, or a more complex one.
-const authChain = Authenticator.createSimpleAuthChain(entityId, address, signature)
+```javascript
+import { Authenticator } from '@dcl/crypto'
+import { createCatalystClient } from 'dcl-catalyst-client'
+import { createFetchComponent } from 'dcl-catalyst-client/dist/client/utils/fetcher'
+import * as EthCrypto from 'eth-crypto'
+import { EntityType } from '@dcl/schemas'
+import { PROFILE_METADATA, PROFILE_POINTERS } from './data/inputs'
 
-// Build the client
-const catalyst = await CatalystClient.connectedToCatalystIn('mainnet')
-// Note: this operation is expensive, so try to store the created catalyst client somewhere, instead of re-building for each every request
+async function resolveClient() {
+  // Build the client, Node is harcoded for simplicity
+  const fetcher = createFetchComponent()
+  const catalyst = await createCatalystClient({ url: 'https://peer-ec2.decentraland.org', fetcher })
 
-// Build entity and group all files
-const { entityId, files } = await catalyst.buildEntity({type: EntityType.*, pointers, files: contentFiles, metadata })
+  return await catalyst.getContentClient()
+}
 
-// Build the deploy data
-const deployData = { entityId, files, authChain }
+const identity = { privateKey: 'privatekey', address: '0xfbf2b0392d969db533189b596708ba9ba7f4e3cd' }
 
-// Deploy the actual entity
-await catalyst.deployEntity(deployData)
+const content = await resolveClient()
 
-```
+const { entityId, files } = await content.buildEntity({
+  type: EntityType.PROFILE,
+  pointers: PROFILE_POINTERS,
+  metadata: PROFILE_METADATA
+})
 
-## Contributing
+// This is up to you. You will need to figure out how to make the owner of the pointer sign the entity id
+const messageHash = Authenticator.createEthereumMessageHash(entityId)
+const signature = EthCrypto.sign(identity.privateKey, Buffer.from(messageHash).toString('hex'))
 
-### Build and test
+// You can then create a simple auth chain like this, or a more complex one.
+const authChain = Authenticator.createSimpleAuthChain(entityId, identity.address, signature)
+const deployData = { entityId, files, authChain }
 
+// Deploy the actual entity
+await content.deploy(deployData)
 ```
-npm install
-npm run build
-npm run test
-```
-
-### [Releases](https://registry.npmjs.org/dcl-catalyst-client)
-
-#### Stable Releases
-
-To publish a new release, a tag following [SemVer](https://semver.org/) must be done in `master` branch following the format: `MAJOR.MINOR.PATCH` and that will trigger a Github Workflow that publishes the new version of the library, tagging it as `latest`.
-
-#### Master Releases
-
-Every commit to `master` branch triggers a NPM Publish with the beta version following the convention `NEXT_MAJOR.NEXT_MINOR.NEXT_PATCH-TIMESTAMP.commit-COMMIT_SHA`, tagging it as `next`.
-
-#### Tag Releases
-
-If you need to publish a NPM package in a work in progress commit, then you can create a git tag, and that will trigger an automatically NPM publish following the convention `NEXT_MAJOR.NEXT_MINOR.NEXT_PATCH-TIMESTAMP.commit-COMMIT_SHA` and tagging it on NPM with your custom tag: `tag-CUSTOM_TAG`.