Replies: 4 comments
-
I think this is a great idea! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Great idea - I put it on the backlog. No ETA yet. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Seems to be same suggestion as #1055 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Now available in 3.12.0! Thanks for the suggestion! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
When I am modifying or debugging measures, I often create variables or change which variables are used to get the result. I often wind up with variables that are unnecessary in the final result.
Describe the solution you'd like
I'd like some sort of visual indicator in the Expression editor for variables that are not called anywhere else in the expression. I know it doesn't cause a performance issue, just a code readability issue, and it confuses Future Ed sometimes.
It could be a button to highlight unused variables, or even variable chains. Example:
varFirstValue is used by varSecondValue, and that is used in varThirdValue, but none of those can actually impact the results of the measure, they were orphaned debug code or left over from the original version of a measure that got reworked.
Describe alternatives you've considered
I currently just comment out suspect variables and see if I get error messages.
Beta Was this translation helpful? Give feedback.
All reactions