-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.
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
docs: rename 'connect to testnet' section #1677
Conversation
Coverage report
Test suite run success1482 tests passing in 263 suites. Report generated by 🧪jest coverage report action from 6a323cf |
Yeah I think these two should be handled separately. I definitely agree with renaming the page if that's what come from the feedback. Most other docs seem to reference it as a Testnet anyways. The first point around hidden docs probably needs a bit more thought. We have vastly improved our documentation and added a lot more content, but it probably does need a more of a top-down approach now and see what we have and what's missing and whether the structure could be improved. |
@danielbate sounds fair. I'm gonna scope this PR to just renaming the section for now, then. I'll file a separate issue to update the code in the example once beta-5 is officially up. We can then have the code example demonstrate how to interact with a live contract on the beta-5 testnet. |
Opened a discussion: #1690 (comment) |
Coverage Report:
Changed Files:Coverage values did not change👌. |
As it turns out, we already have a page that goes over how one can connect to the Fuel testnet. This section was named as 'Connecting to external node' though. I have renamed it to 'Connecting to Testnet' via this PR.
Some ideas for further improvementThe reason why the lack of these docs was mentioned in the feedback was probably the fact that they are a bit hidden under the 'Provider' section in the sidebar. Maybe we can move 'guides' like this one to a specific section? The 'Cookbook' section is a good candidate but cookbooks are usually reserved for rather advanced examples. Any thoughts?The example on the page itself demonstrates initializing a wallet on the testnet and does not actually interact with any contracts on the testnet or with the testnet node itself. Maybe we should update the example?Update the 'connecting to testnet' example #1690 (comment)Closes #1548