Skip to content

Fix foxglove messages build issue - #121

Merged
nathanaelren merged 2 commits into
mainfrom
fix-foxglove-build
Jul 8, 2026
Merged

Fix foxglove messages build issue#121
nathanaelren merged 2 commits into
mainfrom
fix-foxglove-build

Conversation

@maxwellmlin

@maxwellmlin maxwellmlin commented Jul 8, 2026

Copy link
Copy Markdown
Member

Background: we generate our ROS TypeScript types from source (whatever ROS is currently installed in the container) whenever we do fox build. For more active frontend teams, the better pattern would probably be to commit these types and have someone rebuild/review the updated types regularly. However, I automated this process during the ROS 2 migration since we don't have an active frontend team to do this. This means that if ROS adds new message definitions, the build may occasionally break and you may have to do a fix like this...

Include every package that actually defines messages or services rather then use the previous suffix heuristic.
@maxwellmlin

Copy link
Copy Markdown
Member Author

Should be fine to merge as long as all checks pass.

@nathanaelren
nathanaelren self-requested a review July 8, 2026 17:25

@nathanaelren nathanaelren left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@ChuChuCodes0414 ChuChuCodes0414 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Lgtm

@nathanaelren
nathanaelren merged commit 0f4a865 into main Jul 8, 2026
1 check passed
@nathanaelren
nathanaelren deleted the fix-foxglove-build branch July 8, 2026 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants