Update docs to deprecate V1 and add basic V2 job#229
Update docs to deprecate V1 and add basic V2 job#229
Conversation
|
✔️ Deploy Preview for dreamy-villani-0e9e5c ready! 🔨 Explore the source changes: 25dde27 🔍 Inspect the deploy log: https://app.netlify.com/sites/dreamy-villani-0e9e5c/deploys/6112e99297b0290007a0bf1a 😎 Browse the preview: https://deploy-preview-229--dreamy-villani-0e9e5c.netlify.app |
de218b5 to
c093093
Compare
alexroan
left a comment
There was a problem hiding this comment.
Very informative docs, nice work!
We could structure the pages a little better to reduce the cognitive load in finding what readers need. Some context, maybe an intro page explaining the two formats and what changed, will go a long way to improving the information architecture.
| { url: '/docs/initiators/', title: 'Initiators' }, | ||
| { url: '/docs/jobs/', title: 'Jobs' }, | ||
| { url: '/docs/tasks/', title: 'Tasks' }, | ||
| { url: '/docs/job-specifications/', title: 'Job Specifications [DEPRECATED]' }, |
There was a problem hiding this comment.
I think there's a better way we can structure the deprecated pages. Maybe version 1 and 2 parent pages, with 2 being the default?
There was a problem hiding this comment.
What is a parent page?
There was a problem hiding this comment.
Here's an example of one: https://docs.chain.link/docs/reference-contracts/
Take a look at the menu item, it acts as a parent to sub-pages.
| medianize_data -> submit_to_ea | ||
| ``` | ||
|
|
||
|  |
There was a problem hiding this comment.
This image isn't showing on my local or the generated preview. I believe assets like this are stored in _src/images/.
There was a problem hiding this comment.
This looks great. As we learn more we will probably update something here. We will probably want to update our blogs on this as well with a note about the change.
ie: https://blog.chain.link/build-and-use-external-adapters/
https://www.youtube.com/watch?v=65NhO5xxSZc
https://www.youtube.com/watch?v=4i75Dqbhjvw
Please ping me to change these when this change goes live
| ``` | ||
|
|
||
| - `contractAddress`: the address of the FluxAggregator contract that manages the feed. | ||
| - `precision`: the number of decimal places to be associated the integer value submitted on-chain. |
| confirmations = 6 | ||
| publicKey = "0x79BE667EF9DCBBAC55A06295CE870B07029BFCDB2DCE28D959F2815B16F8179800" | ||
| observationSource=""" | ||
| getrandomvalue [type=vrf]; |
There was a problem hiding this comment.
this might change quite soon, I'd hold off on merging this until we have tested it using ethtx tasks
| ### VRF | ||
|
|
||
| ```toml | ||
| uuid = "123e4567-e89b-12d3-a456-426655440000" |
There was a problem hiding this comment.
this is now called externalJobID and is a universal parameter across all V2 specs. Probably deserves its own little blurb something like
The externalJobID is a optionally user-specified way to deterministically provide an ID of a job. Say for example you want to run the same directrequest job on two different chainlink nodes which have different bridge names. Although the actually spec contents differ slightly, you can use the same externalJobID on both, specify that in your on-chain requests and both nodes will pick it up. If you do not provide one, one will be generated by the node.
|
Looks like we need to add some migration examples in here. @DmitryDao is this something you can do? Show JSON jobs and what their TOML equivalent jobs look like? If no one can, I can take this, but I'd much rather someone else if possible. Perhaps @ZakAyesh? How much node experience do you have? |
I haven't really worked with TOML but I know there are converters for that. Just let me know which migration samples are you talking about and I'll see if I can do something about them. I haven't been working with nodes for a while now though so I might be out of date on the recent updates that are mentioned in these docs. |
| { url: '/docs/jobs/', title: 'Jobs' }, | ||
| { url: '/docs/tasks/', title: 'Tasks' }, |
There was a problem hiding this comment.
Maybe we should call them Jobs V2/Tasks V2 and the old ones Jobs V1/Tasks V1 (at least in the navbar) temporarily? This will help people can move over gradually. Thoughts?
There was a problem hiding this comment.
Yup that seems reasonable
There was a problem hiding this comment.
Thinking about this more, I suspect it's likely to lead to more confusion. Since we have various v1/v2 of other things like ocr v1/v2 or VRF v1/v2. Better to keep the language here as it is
| Please refer to the [V2 jobs page](/docs/jobs) for guidance on how to do this. | ||
|
|
There was a problem hiding this comment.
Do we think we should create a migration guide or tutorial instead of keeping deprecated docs? This is a big deal and people should be aware of it.
There was a problem hiding this comment.
I am creating a migration guide to be included in this PR.
|
|
||
|  |
There was a problem hiding this comment.
I can't figure out how to get this image to work.
| ## What is a Task? | ||
|
|
There was a problem hiding this comment.
I think the new version of tasks has to be updated on a few other pages:
| ### Direct request (eth log) | ||
|
|
There was a problem hiding this comment.
What's the replacement for RunLog in a new version?
There was a problem hiding this comment.
This job type replaces both runlog and ethlog. There's a discussion around whether we rename it to ethlog as thats just a better/more descriptive name than directrequest
| whatsnext: {"Introduction to External Initiators":"/docs/external-initiators-introduction/"} | ||
| --- |
There was a problem hiding this comment.
Do we keep the External Initiators in V2? I mean not only here but all of the relevant pages/docs.
There was a problem hiding this comment.
Yes External Initiators still exist and work with V2 jobs, they probably need a documentation overhaul though.
22f2238 to
26e6ff7
Compare
f872c32 to
b201006
Compare
|
Review pls |
b201006 to
6a7724f
Compare
Co-authored-by: Alex Roan <alex.roan@hotmail.com>
6a7724f to
25dde27
Compare
|
Closed via #292. Thank you for all of the excellent new content! |

No description provided.