docs: update links #457
docs: update links #457
Conversation
| ``` | ||
|
|
||
| Now let's fetch the metadata. | ||
| As an example, let's connect to Polkadot and fetch the chain's metadata for the present highest block. |
There was a problem hiding this comment.
Is this true? Of is this somehow statically defined in capi?
There was a problem hiding this comment.
I'm not sure exactly what you mean. Can you please re-word this question?
There was a problem hiding this comment.
Am I correct in assuming that the example here using Polkadot metadata is gathered at runtime from the network? So this actually is an RPC call that connects to some default node?
Or is everything here coming from the library itself, hard coded values?
There was a problem hiding this comment.
Am I correct in assuming that the example here using Polkadot metadata is gathered at runtime from the network? So this actually is an RPC call that connects to some default node?
Correct
|
Perhaps I am failing CI as you instead wanted dprint to format md files? |
nuke-web3
force-pushed
the
NukeManDan-patch-1
branch
from
0a613ec to
58cf060
Compare
nuke-web3
changed the title
|
Correct: we use dprint for MD formatting. Going to revert the snaphot. Aside from that, this looks great! |
That's generated off of a fixed version of the metadata, which was last refetched about a month ago, so it may very well be fixed in the latest runtime. |
Co-authored-by: T6 <[email protected]>
|
Perhaps a followup pr to update the metadat is in order: links in the docs with |
I see prettier is used in the .vscode setting elsewhere, use it in md too.
Metadata.test.ts.snap -- Found more links issues, but I think this is a generated file, so actually the runtime has the wrong links embedded in them? 😬
If so, can put in redirects on docs for these