Skip to content

Conversation

@Amxx
Copy link
Collaborator

@Amxx Amxx commented Jun 19, 2023

Fixes LIB-876

PR Checklist

  • Tests
  • Documentation
  • Changeset entry (run npx changeset add)

@changeset-bot
Copy link

changeset-bot bot commented Jun 19, 2023

🦋 Changeset detected

Latest commit: 19990eb

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
openzeppelin-solidity Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@Amxx Amxx requested review from ernestognw and frangio June 19, 2023 16:07
const expectedSupply = initialSupply.add(amount);
expect(await this.token.totalSupply()).to.be.bignumber.equal(expectedSupply);
});
const describeBurn = function (description, amount) {
Copy link
Member

Choose a reason for hiding this comment

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

For consistency, I'd suggest:

Suggested change
const describeBurn = function (description, amount) {
function describeBurn (description, amount) {

Non-blocking.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That is not related to this PR. Maybe we can put that in a dedicated "cleanup/consistency" PR?
Otherwize we can do it here, I don't have a strong opinion.

Copy link
Contributor

Choose a reason for hiding this comment

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

This wasn't introduced in this PR so if we want to change it let's do it separately.

Copy link
Member

Choose a reason for hiding this comment

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

Agree in doing it in another PR

@ernestognw
Copy link
Member

It requires a changeset

Copy link
Contributor

@frangio frangio left a comment

Choose a reason for hiding this comment

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

Looks good. Minor comment.

frangio
frangio previously approved these changes Jun 21, 2023
Copy link
Member

@ernestognw ernestognw left a comment

Choose a reason for hiding this comment

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

Sorry for just bringing it up but we talked before about registering the changes needed to migrate to 5.0 and I think this should go into this list.

Did we agree to put it in the CHANGELOG?

@frangio
Copy link
Contributor

frangio commented Jun 22, 2023

If there are any breaking changes that users need to adapt in their code when upgrading, we should put them in a section "How to Upgrade from 4.x" in the changelog.

In this case though users don't need to do anything, so I don't think there is anything we need to mention in that section, beyond what we should mention in the changeset.

This was referenced Sep 10, 2024
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.

3 participants