fix: enforce name uniqueness for bridges in DSL verifier #31
Conversation
This file contains hidden or 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
The `UniquenessTransformer` was only checking `[:sensors]`, `[:controllers]`, and `[:topology]` paths for duplicate names. Bridges, which are registered processes in the same registry, were not being checked. This could cause runtime errors when starting a robot if a bridge had the same name as a controller, sensor, link, joint, or actuator. Now includes `[:parameters]` in uniqueness checking, which catches bridge name conflicts at compile time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
UniquenessTransformerwas only checking[:sensors],[:controllers], and[:topology]paths for duplicate names[:parameters]in uniqueness checking, catching bridge name conflicts at compile timeTest plan
mix check --no-retrypasses