-
Notifications
You must be signed in to change notification settings - Fork 43
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
packages/contracts/utils/ens.ts
Outdated
await ens.setSubnodeRecord( | ||
|
||
// skipping if it is already set | ||
const resolved = await ens.resolver( |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
packages/contracts/utils/ens.ts
Outdated
console.log(`Registering subdomain ${domains[i]}`); | ||
|
||
const resolved = await ens.resolver(ensDomainHash(domains[i])); | ||
if (resolved === resolver.address) { |
There was a problem hiding this comment.
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
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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
Checklist:
CHANGELOG.md
file in the root folder.