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
The nextflow variable don't have to wrapped in braces but it is useful when concatenate variable names with other strings, as the boundaries of the variable name can become unclear wittout the use of ${..}.
In the VARIABLE SUBSTITUTIONS callout I mention this. Similar to bash scripting Nextflow uses the $ character to introduce variable substitutions. The variable name to be expanded may be enclosed in braces {variable_name}, which are optional but serve to protect the variable to be expanded from characters immediately following it which could be interpreted as part of the name. It is a good rule of thumb to always use the {} syntax because it enhances readability and clarity, ensures correct variable interpretation, and prevents potential syntax errors in complex expressions.
Do inputs need to be wrapped in ${...} when used in a script? What is good practise?
The text was updated successfully, but these errors were encountered: