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

only unwrap default values in the mixin extension which have been wrapped by it #22

Merged
merged 1 commit into from
Apr 16, 2020

Conversation

dirk-thomas
Copy link
Member

Fixes #21 which is a regression of #19.

@dirk-thomas dirk-thomas added the bug Something isn't working label Apr 16, 2020
@dirk-thomas dirk-thomas self-assigned this Apr 16, 2020
Copy link

@jacobperron jacobperron left a comment

Choose a reason for hiding this comment

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

Is this something we have to worry about in other packages where unwrap_default_value is used?

@dirk-thomas
Copy link
Member Author

Is this something we have to worry about in other packages where unwrap_default_value is used?

I don't know of any other location where the function is being used. If you know any please point me to them so I can take a look to double check.

@jacobperron
Copy link

If you know any please point me to them so I can take a look to double check.

I'm not aware of any. I was thinking that it would be nice to have the original wrap and unwrap functions deal with this scenario so if it arises in other places we don't have to add similar workarounds. But, I don't have an alternative proposal, so this fix lgtm.

@dirk-thomas dirk-thomas merged commit 03c6f13 into master Apr 16, 2020
@delete-merged-branch delete-merged-branch bot deleted the dirk-thomas/fix-handling-default-values branch April 16, 2020 18:29
@dirk-thomas dirk-thomas added this to the 0.1.8 milestone Apr 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging this pull request may close these issues.

Colcon performs recursive discovery despite specifying --paths
2 participants