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
Sometimes it would be useful to be able to use a list variable so that it
would be considered a scalar variable containing a list. Possible use cases
include getting the length of the list variable using built-in 'Get Length'
keyword and modifying the list with different keywords from Collections
library.
A simple solution is using ${LIST} syntax for using @{LIST} as a scalar. We
don't need to add any new syntax and this is also trivial to implement. All
that needs to be done is checking is a variable @{XXX} set and returning
its value, if resolving ${YYY} fails. To make this change 100% backwards
compatible (and more logical in general), we should always return the value
of ${NAME} if it's set, regardless is @{NAME} defined or not.
The text was updated successfully, but these errors were encountered:
Sometimes it would be useful to be able to use a list variable so that it
would be considered a scalar variable containing a list. Possible use cases
include getting the length of the list variable using built-in 'Get Length'
keyword and modifying the list with different keywords from Collections
library.
A simple solution is using ${LIST} syntax for using @{LIST} as a scalar. We
don't need to add any new syntax and this is also trivial to implement. All
that needs to be done is checking is a variable @{XXX} set and returning
its value, if resolving ${YYY} fails. To make this change 100% backwards
compatible (and more logical in general), we should always return the value
of ${NAME} if it's set, regardless is @{NAME} defined or not.
The text was updated successfully, but these errors were encountered: