2
 Followers
8
 Likes

Expression Editor add text to the end by default

Service Studio
On our radar

When editing an existing expression, it would save some time if the variable/property that is double-clicked could be added to the end of the string rather than at index 0 as is currently the case. 

With longer expressions, this will negate the need to scroll down to the end of the expression before adding the required variable/property.

Created on 22 Jun
Comments (10)

It doesn't get added to Index 0. It gets added to wherever the cursor currently is, or replaces the selected text, which is the perfect and expected behavior.

J.Ja

Thanks Justin. That is correct. What I meant is that the cursor's initial position when opening the expression should be set to the end of the current expression.

Ah, gotcha! Yes, that makes sense.


J.Ja

Merged this idea with 'Place the cursor at the end of the string in a filter when created from an aggregate column' (created on 25 Jun 2018 13:21:55 by Ouen Worth)

When a filter is created in an aggregate by selecting the filter option in the drop-down of a column, the expression editor opens with the entities attribute already completed and an equal sign.

The cursor is currently being placed at the beginning of the line instead of the line which reduces the workflow benefit of this feature.

Please, can it be placed at the end of the line so that the filter criteria can be directly entered without any additional keystrokes or mouse clicks?



Merged from 'Place the cursor at the end of the string in a filter when created from an aggregate column' (idea created on 25 Jun 2018 13:21:55 by Ouen Worth), on 26 Jun 2018 03:19:33 by Justin James

Ouen,


Can this idea be the same as Expression Editor add text to the end by default?



Merged from 'Place the cursor at the end of the string in a filter when created from an aggregate column' (idea created on 25 Jun 2018 13:21:55 by Ouen Worth), on 26 Jun 2018 03:19:33 by Justin James

Here, let me merge that for you. :)

J.Ja

The concept is similar when looking at the Expression Editor as a whole when opening it anytime which is probably the reason why the behaviour presents itself in the filter scenario.

Changed the category to Service Studio


Changed the status to
On our radar


Thanks for the idea!

views
269
Followers
2