Skip to content

[ports] Add behaviour and name to port conversion error messages - #517

Merged
sea-bass merged 1 commit into
splintered-reality:develfrom
eholum:port-type-remapping
Sep 17, 2026
Merged

sea-bass merged 1 commit into
splintered-reality:develfrom
eholum:port-type-remapping

Conversation

@eholum

@eholum eholum commented Sep 17, 2026 •

Copy link
Copy Markdown
Contributor

As our behavior trees have gotten larger we've sometimes run into port value errors that can be difficult to localize, as they get buried in trees. Specifically:

Cannot convert Value:'' to type <class 'float'>

This change just updates those error messages to include the behavior type and name to make finding invalid port entries easier. Both things were already available in the function, so no other changes required.

After:

Cannot convert Value '' to type <class 'float'> in 'MyGreatBehavior' (name='great_behavior_node')

@sea-bass sea-bass left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks! I would almost do the message the opposite:

Failed to do X In behavior name "foo" (type MyGreatBehaviour)

@eholum
eholum force-pushed the port-type-remapping branch from 9b6a8ef to 4c55d9e Compare September 17, 2026 18:34
@eholum
eholum force-pushed the port-type-remapping branch from 4c55d9e to 0f1a7e3 Compare September 17, 2026 18:37
@sea-bass

Copy link
Copy Markdown
Member

Looks like something done broke on main. Gonna merge this and fix the rest after

@sea-bass
sea-bass merged commit 91c44bd into splintered-reality:devel Sep 17, 2026
4 of 5 checks passed
@eholum
eholum deleted the port-type-remapping branch September 17, 2026 19:23
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.

2 participants