You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is a possible technique inspired by the JSDoc standard (https://en.wikipedia.org/wiki/JSDoc) that can be used in September 2025 version of Power BI Desktop and shows the parameters in the function description:
122
122
```
123
123
/// Convert from Celsius(°C) to Fahrenheit(°F)
124
-
/// @param temperature – The temperature in Celsius
124
+
/// @param {decimal} temperature – The temperature in Celsius
125
125
/// @returns The temperature converted to Fahrenheit
126
126
FUNCTION CelsiusToFahrenheit = ( temperature: DOUBLE ) =>
127
127
( temperature * ( 9 / 5 ) ) + 32
128
128
```
129
129
130
-
Here is the technique adopted for parameters by Tabular Editor 3 in September 2025 release:
130
+
These would be the rule to follow in DAX to use JSDoc-style comments:
131
+
- Use `///` to start a comment block for a function.
132
+
- Use `@param` to describe each parameter of the function. You can also use `@arg` and `@argument` as parameter tags.
133
+
-_(Optional)_ After `@param`, you may include the type of the parameter within curly braces `{}`.
134
+
- The word after `@param` and the optional type is the name of the parameter being described.
135
+
-_(Optional)_ After the parameter name, use a dash `–` (en dash) to separate the name from its description.
136
+
- Use `@returns` to describe the return value of the function. You can also use `@return` as a synonym.
137
+
138
+
Here is the technique adopted for parameters by Tabular Editor 3 in September 2025 release, but we expect Tabular Editor 3 to support the JSDoc-style comments in future releases:
0 commit comments