feat: add info disclaimer to moveToJointPositions widget (#75)#76
Merged
Conversation
|
DTCurrie
approved these changes
May 22, 2026
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
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.
Adds an info disclaimer tooltip to the
moveToJointPositionswidget clarifying that joint position limits are derived from arm kinematics only and do not reflect motion service limit overrides.Closes #75
Frontend
move-to-joint-positions.svelte: Added aTooltipwith an information icon next to the "Joint Positions" header. The tooltip text reads: "Joint position limits are based solely on the arm kinematics and do not take into account motion service limit overrides." Follows the same pattern used for the existing "Quick set" tooltip in the same component.Testing
move-to-joint-positions.spec.tsverifying the disclaimer text is rendered.pnpm lintandpnpm checkpass. Unit tests require Playwright browser (not available in this CI environment) but follow existing test patterns.DRI
@mattmacf98 is the responsible engineer for this PR.