More than once I've been baffled while debugging or inspecting code how something could ever work, or works like it does, when finally realizing an expression continues "below the fold". It would be nice if Service Studio would clearly indicate, using an ellipsis or arrow icon or the like, that an expression is continued on the next line. This goes for input parameter assignments, normal assignments, screen expressions etc.
Example:
a > 2
and a < 4
Service Studio will only show "a > 2" without an indication that there's more. Then debug, and have a = 4 and try to find out why the condition fails...
Currently, Condition, description etc. are just displaying the only first one line of them in the property area, at the right bottom corner of screen. Therefore, sometimes we fail to recognize that there are two or more lines in condition, description etc.
We’re thinking that it’s preferable to display some mark or sign, for noticing two or more lines’ existence, at the property area.How do you think about this kind of idea ?
Changed the category to Service Studio and the status to
Hello Takeshi,
It totally makes sense, I had that problem a couple times myself ;)
Thanks for the idea!
Good idea. Though we have some internal coding styles that at least mandate putting an "and" or "or" etc. on the first line, depending on your view this may be invisible.
Hello TAKESHI,
Thanks a lot for this idea. I'm happy to announce that this was already implemented and was released in Service Studio 10.0.907.0 version.
You can check a public thank you for your contribution in this version's release notes:
https://success.outsystems.com/Support/Release_Notes/Development_Environment/Development_Environment_10.0.907.0
Hope you like it!
Hello Vasco !
Thank you for all, your kindness, accepting my idea and implementing it.
It’s our pleasure to help others in this way.
Hello Kilian,
Thanks a lot Vasco! The only downside is I now need a different reason for our junior devs to adhere to our coding standards of not putting the "and" (as in my example) on a second line :))).