This repository has been archived by the owner on Sep 28, 2023. It is now read-only.
Namespace with maliput
#4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 8, 2021
francocipollone
previously approved these changes
Oct 11, 2021
francocipollone
approved these changes
Oct 11, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Part of maliput/maliput_infrastructure#232
Favoring downstream consumption of maliput backends, contents of this workspace are namespace-d with
maliput. See the readme instructions for a list of applied changes.For reviewers: I have split changes in multiple commits but they don't compile unless you take them all. It's a big change, I know but I couldn't find any other split that is easy to review and works. I apologize in advance!