Recursively load all transformer configurations. #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently configuration files are loaded recursively from all bundles, but the transformer configuration is only loaded from the most specific bundle. I would suggest to handle the transformer configuration in the same way as the orogen configs.
Not sure what the intended behavior is though. The suggested change will definitely change that behavior and probably cause issues when an previously unused transforms.rb is present in an included bundle.