Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow the implicit import function library in both config and application script #940

Closed
pditommaso opened this issue Nov 22, 2018 · 4 comments
Labels

Comments

@pditommaso
Copy link
Member

The goal of this feature is to allow the definition of custom library of functions that are automatically imported in the global scope of either the nextflow.config file and the main application script.

This would allow users to define custom helper functions without the hassle to explicitly import then as Java imports.

Additionally it should allow the usage of implicit nextflow objects i.e. params, workflow, baseDir, workDir and log when available.

@stale
Copy link

stale bot commented Apr 27, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Apr 27, 2020
@pditommaso pditommaso added stale and removed wontfix labels Apr 27, 2020
@stale stale bot closed this as completed Jun 26, 2020
@thedam
Copy link

thedam commented Apr 20, 2022

still this feature is not valid? (functions inside config)

@risoms
Copy link

risoms commented Nov 7, 2024

@pditommaso Has this been introduced into Nextflow? I'm coming across the same error.

@bentsherman
Copy link
Member

The lib directory was implemented for scripts but not for config files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants