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

feat: allowed specifying renderBody via constructor #1548

Merged

Conversation

alestiago
Copy link
Contributor

Description

Allows setting renderBody via constructor.

Checklist

  • The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
  • I have read the Contributor Guide and followed the process outlined for submitting PRs.
  • I have updated/added tests for ALL new/updated/fixed functionality.
  • I have updated/added relevant documentation in docs and added dartdoc comments with ///.
  • I have updated/added relevant examples in examples.

Breaking Change

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

Related Issues

Copy link
Member

@spydon spydon 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, just one suggestion!

}) : super(priority: priority) {
this.paint = paint ?? (Paint()..color = defaultColor);
}

static const defaultColor = Color.fromARGB(255, 255, 255, 255);
Copy link
Member

Choose a reason for hiding this comment

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

I think we can skip this one and rely on the default color of HasPaint

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 think we should do this on another PR since this would be a breaking change. In addition, it is out of the scope of the PR.

Copy link
Member

Choose a reason for hiding this comment

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

Sounds good, I was thinking of it since you did some changes to paint in this PR too

Copy link
Contributor Author

@alestiago alestiago Apr 15, 2022

Choose a reason for hiding this comment

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

Oopsy. Did I change something? I believe I only reordered the constructor to be right after the class declaration.

@spydon
Copy link
Member

spydon commented Apr 15, 2022

Just the merge conflict that needs to be solved, other than that I think this is ready to be merged!

@spydon spydon enabled auto-merge (squash) April 15, 2022 07:46
auto-merge was automatically disabled April 15, 2022 07:56

Head branch was pushed to by a user without write access

@spydon spydon merged commit ceb7266 into flame-engine:main Apr 15, 2022
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.

2 participants