Improve error when raw2derived argument has no type#1135
Conversation
coretl
left a comment
There was a problem hiding this comment.
Please could I also have a similar test in test_multi_derived_signal where there are no type hints?
I don't follow - if I add it there it will still test same DerivedSignalFactory which is already tested in test_single_derived |
Yes, but this captures the use case (need to check we get errors when invoked via Also, would you mind if I let some AI loose on a code review of this PR? |
|
yay AI review! go for it. |
yes please
I'll trigger it, but I'll review it's review before you take any action on it... |
|
Claude finished @coretl's task in 2m 40s —— View job Code Review CompleteSummaryI've reviewed PR #1135 which improves error messages when Key findings: ✅ Strengths:
Detailed feedback posted as inline comments on specific lines. |
oliwenmandiamond
left a comment
There was a problem hiding this comment.
This looks to be a big improvement of derived signal logic and error handling, thank you!
I would link my issue so it also closes that and update the PR title to be to make improvements to derived signal as we have moved beyond just fixing an error message now
Closes #1108