Skip to content

Conversation

lhutton1
Copy link
Contributor

Fixes a merge conflict between #16981 and #17003.

Closes #17038

cc @ekalda @Anndrey24

Fixes a merge conflict between apache#16981 and apache#17003.

Change-Id: Ifcc983ef0b8c00250568a048fd682933adfdcde4
Copy link
Contributor

@Lunderberg Lunderberg left a comment

Choose a reason for hiding this comment

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

Thank you for the fix!

Looking at the breakage, it looks like it was caused by the addition of a required function parameter in #16981, along with the addition of new calls to that function in #17003. This breakage could have been avoided if the new function parameter had been optional instead of required.

Unless there is a significant reason not to do so, I think new function parameters should be optional, with a default value that reproduces the previous behavior. Doing so would avoid this type of breakage in the future, and would also improve backwards compatibility with external callers, when the function is part of a public-facing API

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