Forum Discussion
17 Replies
- tstackFormer Employee
You should be able to reference the other library through the
lib
variable. Is that not working?For example, if you this as the library
helper.expr
:{ chefify: x => x + ' bork! bork! bork!' }
You should be able to reference it from another library, like so:
{ msg: () => lib.helper.chefify('Hello, World!') }
Note that if the references are not in functions, but directly in the top-level expression, youâll need to ensure the libraries are listed in the right order in the pipeline properties.
- ayush_vipulNew Contributor III
I found a better way to achieve what i was look for.
But thanks for highlighting this.@tstack
- ayush_vipulNew Contributor III
I have a use case where a child pipeline has multiple expr files.
I want to pass a value to the child pipeline using which my chiled pipeline would choose one of the expression library.
is there a way to do it ?- tstackFormer Employee
In the child pipeline properties, add a parameter that youâll use to specify the library to load. Then, in the âExpression Librariesâ section, add a path that uses the parameter you just created. Youâll probably also want to set the name of the imported library using the âAsâ column. In the screenshot below, the parameter is
config
and defaults to the library filedev.expr
and the library can be referenced vialib.conf
in expressions:In the parent pipeline, youâll pass the
config
parameter with the library paths that you want. In the screenshot below, there are two documents entering the PipeExec with âdev.exprâ and âprod.exprâ as the paths. So, the child will execute first with the âdevâ library and then with the âprodâ library.
- ayush_vipulNew Contributor III
Is there a way to declare methods with global scope in expression library.
Is nesting multiple libraries together a good preactice ?- tstackFormer Employee
Do you mean without the
lib.libname
prefix? No, libraries are always imported under thelib
object.Iâm not sure what you mean by this, can you give an example?