Skip to content

Reference "core adapter" instead of "adapter" #113

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
StephenFluin merged 1 commit into from
May 30, 2021
Merged

Reference "core adapter" instead of "adapter" #113

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/Oracle Jobs/job-specifications.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ This example shows the two main components of a spec: initiators and tasks. [Ini

In the example above, we see that the only initiator is a RunLog. This means that the spec can only be started when a specific event log is emitted from a specified address. The specified address will be the address of the oracle contract on Ropsten, which manages requests from contracts and responses from Chainlink nodes.

The five tasks (referred to as [adapters](../adapters/)/) in the example above follow a common pattern for requesting data from the Chainlink network, and returning a single result. Each task takes three fields: `type`, `confirmations`, and `params`. The `type` is the adapter or [bridge](../glossary/#bridge) name and is required. `confirmations` is optional, and will default to 0. `params` is also optional, and will default to an empty object if not specified. See the [adapters](../adapters/) page for a complete list of `params` for each adapter.
The five tasks (referred to as [core adapters](../adapters/)) in the example above follow a common pattern for requesting data from the Chainlink network, and returning a single result. Each task takes three fields: `type`, `confirmations`, and `params`. The `type` is the adapter or [bridge](../glossary/#bridge) name and is required. `confirmations` is optional, and will default to 0. `params` is also optional, and will default to an empty object if not specified. See the [core adapters](../adapters/) page for a complete list of `params` for each adapter.

1. The **HTTPGet** adapter uses the value in the `get` field to perform a standard HTTP GET request at the value specified. The body of that result is passed on to the next task, JSONParse.
2. The **JSONParse** adapter takes a dot-delimited string or an array of strings, and will walk the given path to store the value at the end. In this case, there is only one field to save, "last". JSONParse will then pass the value stored in the "last" field to the Multiply adapter.
Expand Down