Skip to content

Conversation

@bee344
Copy link
Contributor

@bee344 bee344 commented Nov 7, 2025

📝 Description

Updated hardhat docs with latest functionality. Links are broken until a new hardhat release is done on Monday. Functionality is already present on pre5, with the only difference being the sample project config.

🔍 Review Preference

Choose one:

  • ✅ I have time to handle formatting/style feedback myself
  • ⚡ Docs team handles formatting (check "Allow edits from maintainers")

🤖 AI-Ready Docs

If content changed, regenerate AI files:

  • ✅ I ran python3 scripts/generate_llms.py
  • ⚡ Docs team will regenerate (check "Allow edits from maintainers")

✅ Checklist

@bee344 bee344 requested a review from a team as a code owner November 7, 2025 14:45
},
polkadotHubTestnet: {
polkavm: true,
polkadot: true,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this really a boolean here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@eshaben eshaben requested a review from a team November 7, 2025 19:58
@nhussein11
Copy link
Collaborator

nhussein11 commented Nov 7, 2025

Hi @bee344! I'll temporarily (and softly) block this PR until we get this resolved:

Looping in @UtkarshBhardwaj007 because, based on our last call, I understand we agreed on having docs for the incoming hackathon, but those were supposed to be added to the survival guide, not the official docs, right?

Edit: or maybe this has nothing to do with the hackathon yet? and @bee344 wanted to create a hot-fix due to the hardhat situation?

@bee344
Copy link
Contributor Author

bee344 commented Nov 7, 2025

@nhussein11 yes, it's linked to the hackathon. Besides that, the docs are very outdated since there have been a lot of changes lately, so I don't see the harm in updating them to reflect the current state of the plugin.

It does take into account a future release (0.2.0-pre6), but the only change that comes with that is an updated readme and updated projects generated by the CLI tool.

--8<-- 'code/develop/smart-contracts/dev-environments/hardhat/hardhat.config.js:6:7'
...
--8<-- 'code/develop/smart-contracts/dev-environments/hardhat/hardhat.config.js:12:24'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check line numbers here.

Image

1. Update the Hardhat configuration file to add the local network as a target for local deployment:
```javascript title="hardhat.config.js" hl_lines="13-16"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check line numbers again.

Image

4. Update your Hardhat configuration file with network settings for the Polkadot network you want to target:
```javascript title="hardhat.config.js" hl_lines="18-22"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check line numbers last time :-)

@UtkarshBhardwaj007
Copy link
Collaborator

Hi @bee344! I'll temporarily (and softly) block this PR until we get this resolved:

Looping in @UtkarshBhardwaj007 because, based on our last call, I understand we agreed on having docs for the incoming hackathon, but those were supposed to be added to the survival guide, not the official docs, right?

Edit: or maybe this has nothing to do with the hackathon yet? and @bee344 wanted to create a hot-fix due to the hardhat situation?

Hey @nhussein11 we did plan to do this directly in the main docs as discussed in the meeting. We will not do this in the beta docs because we don't want to share that externally yet. And also as Beto said this documentation was pretty dated anyway.

@nhussein11
Copy link
Collaborator

nhussein11 commented Nov 10, 2025

@UtkarshBhardwaj007, ah, I understood that this update was for the hackathon survival guide, but in anyt case I think we should have some content for the hackathon somewhere (it doesn't really matter where). Thanks!

Copy link
Collaborator

@nhussein11 nhussein11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bee344 facing this issue when reviewing the PR
image


```bash
npm install --save-dev @parity/hardhat-polkadot@latest
npm install --save-dev @parity/hardhat-polkadot@0.2.0-pre6

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That now needs to be changed to 0.2.0, right?


```bash
npm install --save-dev @parity/hardhat-polkadot@0.1.9
npm install --save-dev @parity/hardhat-polkadot@0.2.0-pre6

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That now needs to be changed to 0.2.0, right?

@nhussein11
Copy link
Collaborator

Closed in favor of #1227

@nhussein11 nhussein11 closed this Nov 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants