Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

docs: add missing pointers to the Files API calls #1173

Merged
merged 1 commit into from
Jan 10, 2018
Merged

Conversation

daviddias
Copy link
Member

No description provided.

@ghost ghost assigned daviddias Jan 10, 2018
@ghost ghost added the status/in-progress In progress label Jan 10, 2018
@daviddias daviddias merged commit 8632030 into master Jan 10, 2018
@daviddias daviddias deleted the missing-pointers branch January 10, 2018 18:34
@ghost ghost removed the status/in-progress In progress label Jan 10, 2018
MicrowaveDev pushed a commit to galtproject/js-ipfs that referenced this pull request May 22, 2020
This is a round up of the remaining async/await PRs along with some cleanup and docs fixes.

resolves ipfs#1103
resolves ipfs-inactive/js-ipfs-http-client#1122
resolves ipfs-inactive/js-ipfs-http-client#1158 (hopefully!)
closes ipfs-inactive/js-ipfs-http-client#1164
closes ipfs-inactive/js-ipfs-http-client#1165
closes ipfs-inactive/js-ipfs-http-client#1166
closes ipfs-inactive/js-ipfs-http-client#1169
closes ipfs-inactive/js-ipfs-http-client#1170
closes ipfs-inactive/js-ipfs-http-client#1172

BREAKING CHANGE: The `log.tail` method now returns an async iterator that yields log messages. Use it like:

```js
for await (const message of ipfs.log.tail()) {
  console.log(message)
}
```

BREAKING CHANGE: The response to a call to `log.level` now returns an object that has camel cased keys. i.e. `Message` and `Error` properties have changed to `message` and `error`.

BREAKING CHANGE: Dropped support for go-ipfs <= 0.4.4 in `swarm.peers` response.

BREAKING CHANGE: The signature for `ipfs.mount` has changed from `ipfs.mount([ipfsPath], [ipnsPath])` to `ipfs.mount([options])`. Where `options` is an optional object that may contain two boolean properties `ipfsPath` and `ipnsPath`. The response object has also changed to be camel case. See https://docs.ipfs.io/reference/api/http/#api-v0-mount.

BREAKING CHANGE: Default ping `count` of 1 in client has been removed. The default ping count is now whatever the IPFS node defaults it to (currently 10). If you specifically need 1 ping message then please pass `count: 1` in options for `ipfs.ping()`.

BREAKING CHANGE: Multi parameter constructor options are no longer supported. To create a new IPFS HTTP client, pass a single parameter to the constructor. The parameter can be one of:

* String, formatted as one of:
    * Multiaddr e.g. /ip4/127.0.0.1/tcp/5001
    * URL e.g. http://127.0.0.1:5001
* [Multiaddr](https://www.npmjs.com/package/multiaddr) instance
* Object, in format of either:
    * Address and path e.g. `{ apiAddr: '/ip4/127.0.0.1/tcp/5001': apiPath: '/api/v0' }` (Note: `apiAddr` can also be a string in URL form or a Multiaddr instance)
    * Node.js style address e.g. `{ host: '127.0.0.1', port: 5001, protocol: 'http' }`
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant