Skip to content
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

Fix/deployment script #330

Merged
merged 5 commits into from
Mar 23, 2023
Merged

Fix/deployment script #330

merged 5 commits into from
Mar 23, 2023

Conversation

mathewmeconry
Copy link
Contributor

Description

Please include a summary of the change and be sure you follow the contributions rules we do provide here

Task: ID

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • I have selected the correct base branch.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • Any dependent changes have been merged and published in downstream modules.
  • I ran all tests with success and extended them if necessary.
  • I have updated the CHANGELOG.md file in the root folder.
  • I have tested my code on the test network.

Rekard0
Rekard0 previously approved these changes Mar 13, 2023
Copy link
Contributor

@Rekard0 Rekard0 left a comment

Choose a reason for hiding this comment

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

LGTM!

await ens.setSubnodeRecord(

// skipping if it is already set
const resolved = await ens.resolver(
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't get this check ! The above if (resolved === resolver.address) { is a great fix, but this one, I couldn't imagine when this would be worth it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This one is necessary because the loop fails if we use a subdomain for one of the ENS configurations. e.g. plugins.dao.eth.
While registering plugins.dao.eth it would try to register dao.eth which already exists and fail

console.log(`Registering subdomain ${domains[i]}`);

const resolved = await ens.resolver(ensDomainHash(domains[i]));
if (resolved === resolver.address) {
Copy link
Contributor

Choose a reason for hiding this comment

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

could you call this resolver ? resolved seems like something was resolved.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I had to change it to resolvedResolver because resolver is used by the Resolver deployment earlier in the script

Rekard0
Rekard0 previously approved these changes Mar 14, 2023
Copy link
Contributor

@Rekard0 Rekard0 left a comment

Choose a reason for hiding this comment

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

LGTM

@mathewmeconry mathewmeconry merged commit 4cdf978 into develop Mar 23, 2023
@mathewmeconry mathewmeconry deleted the fix/deployment_script branch March 23, 2023 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants