Skip to content

Latest commit

 

History

History
265 lines (195 loc) · 9.5 KB

MIGRATION.md

File metadata and controls

265 lines (195 loc) · 9.5 KB
Raw

Migration Guide

Table of contents:

The on-going list of breaking changes from current major to next one can be consulted at the end of the document. You are encourage to fix deprecation notices right now (when available).

From @dfuse/eosws-js to @dfuse/client

The first step is to remove the old library from your package and install the new version. Examples below are using Yarn, NPM is similar.

yarn remove @dfuse/eosws-js
yarn add @dfuse/client

Next step is to rename all imports to the new library. So, rename all instances of @dfuse/eosws-js to @dfuse/client using a global search & replace in your editor.

After having change the import/require clauses, it's time to change the client. Indeed, we now have a full fledge dfuse Client and the way to create it has changed. The createEoswsSocket was replaced with a createDfuseClient. The signature of this new call is completely different than the old one.

In fact, the entire philosophy of the client has changed. We now deal with an API key instead of an API token. The client will manage all aspect of the lifecycle of an API token. It will retrieve one from a store (configurable with sane defaults on Web environment), ensure it's freshness as well as always ensuring that all underlying low-level call are always performed using a valid API token.

The old code looks like:

const client = new EoswsClient(
  createEoswsSocket(() => new WebSocket(`wss://${endpoint}/v1/stream?token=${token}`))
)

Convert that to the following:

const client = createDfuseClient({
  apiKey: "Paste your API key here",
  network: "mainnet", // Valid values are: `mainnet`, `jungle`, `kylin` or an host name
})

Notice You should replace the sequence of characters Paste your API key here in the script above with your actual API key obtain from https://app.dfuse.io. A valid API key starts with either mobile_, server_ or web_ followed by a series of hexadecimal character (i.e.) web_0123456789abcdef). Note If you were customizing the WebSocket instance, it's still possible but will need to pass a custom webSocketFactory option:

const client = createDfuseClient({
  ...,
  streamClientOptions: {
    socketOptions: {
      webSocketFactory: async (url: string) => { new WebSocket(...) },
    }
  }
})

If you are in a Node.js environment, you will have to provide a fetch compatible function an a WebSocket client. We suggest the node-fetch and ws libraries. For a quick configuration path, simply define the following on the global scope:

global.fetch = require("node-fetch")
global.WebSocket = require("ws")

Note Don't forget to add those libraries to your package if you don't already have them.

For more details and alternative configuration options for those values, look at the Node.js Section on the documentation.

Once you have the new client, the next step is to convert the actual usage to the new API.

First, calls to connect and disconnect should be completely removed. The client automatically connect/disconnect the stream based if there is active streams or not.

Then, rename the following client methods:

  • getActionTraces -> streamActionTraces
  • getTableRows -> streamTableRows
  • getTransactionLifecycle -> streamTransaction

Now, calling this method returns a Stream object that does not have an onMessage anymore. Instead, the onMessage callback should be moved to the method directly.

So, from this:

const stream = client.getActionTraces(...).onMessage((message) => { ... })

You should now have this instead:

const stream = client.streamActionTraces(..., (message) => { ... })

The stream now starts as soon as you call the streamXXX method. The old behavior of starting the stream when calling onMessage is not supported anymore.

The onMessage will receive the exact same output as before, so you should not have to do anything.

The options it was possible to pass to the socket when creating it in the old library must now be passed to the streamClientOptions.socketOptions field when creating the client.

So from this:

const client = new EoswsClient(createEoswsSocket(socketFactory, {
  onInvalidMessage: (...) => { ... },
  onReconnect: (...) => { ... },
  onClose: (...) => { ... },
  onError: (...) => { ... },
}))

You should now have this instead:

const client = createDfuseClient({
  ...,
  streamClientOptions: {
    socketOptions: {
      onInvalidMessage: (...) => { ... },
      onReconnect: (...) => { ... },
      onClose: (...) => { ... },
      onError: (...) => { ... },
    }
  }
})

On the model part, the req_id on OutboundMessage type is now a required field. It must be provided at all time.

There have been small modification to the model to fit with actual dfuse documentation. Those changes only affect typings and not the actual runtime.

The dfuse/client-react-example was converted from the old library to the new one. Check this commit to see the changes that was required to pass from @dfuse/eosws-js to @dfuse/client-js.

From @dfuse/client@0.2.0 to @dfuse/client@0.2.1

Might break compilations on some projects but occurs in bug fix version bump considered bug against nodeos and dfuse API real typings.

You will now get compilations errors around some models, mainly around optional fields that were flagged as required before and handling of number serialization JSON (number > uint32 get serialized as a string instead of a number by nodeos).

Simply update by fixing the compilations errors, re-working your logic to handle those corner cases that were ignored before.

From @dfuse/client@0.2.2 to @dfuse/client@0.2.3

Might break compilations on some projects but occurs in bug fix version bump considered bug against dfuse API real typings.

You will now get compilations errors around ActionTraceData object, mainly around ops fields.

Renames:

  • dbOps => dbops
  • ramOps => ramops
  • dtrxOps => dtrxops
  • tableOps => tableops

There is a also a some string fields, all op fields that are now restricted to only their valid set of strings.

Simply update by fixing the compilations errors, which is a plain rename.

From @dfuse/client@0.2.3 to @dfuse/client@0.2.4

Might break compilations on some projects but occurs in bug fix version bump considered bug against dfuse API real typings.

You will now get compilations errors around some models, mainly around action trace fields. Also, the ActionTraceData now takes only one generic parameter versus 2 before, the second one can be removed, was used to type ActionTraceDbOp row's data but it's always an hexadecimal encoded string.

Simply update by fixing the compilations errors, re-working your logic to handle those corner cases that were ignored before.

From @dfuse/client@0.2.x to @dfuse/client@0.3.0

Some types were rename, here the massive rename that can be done:

  • Rename any occurrences of RAMPOp type to RamOp.
  • Rename any occurrences of DBOp type to DbOp.
  • Rename any occurrences of ConnectOptions type to SocketConnectOptions

If you had the onInvalidMessage socket options set, simply remove it, it's not used anymore.

Ensure that you validate the type of each message you receive through dfuse Stream API (streamXXX methods) to ensure you only deal with message you care about.

If you had a dependency on Socket class, the type for send and SocketMessageListener are now looser accepting any type instead of only dfuse Stream API types.

From @dfuse/client@0.3.x tonext`

The outbound message factory functions were deprecated. There is no replacement for this, we assume you don't have to create the outbound messages yourself.

They have little usefulness right now since no public methods on the DfuseClient accepts directly an outbound message.

Contact us if you would like a revision of this decision. Removed exported functions are:

  • getHeadInfoMessage
  • getTableRowsMessage
  • getActionTracesMessage
  • getTransactionLifecycleMessage

Using a shortcut value in DfuseClientOptions endpoint field is now deprecated and will not work correctly in this version.

You should replace it with the fully qualified endpoint value:

  • mainnet becomes mainnet.eos.dfuse.io
  • kylin becomes kylin.eos.dfuse.dfuse.io

The op field of RamOp type has been removed. Use a combination of family and action to take your decision.