-
Notifications
You must be signed in to change notification settings - Fork 630
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
Fix closure rendering in yaml and json config #5408
Conversation
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
✅ Deploy Preview for nextflow-docs-staging canceled.
|
Signed-off-by: Ben Sherman <bentshermann@gmail.com>
if( value instanceof Map ) { | ||
final map = value as Map | ||
final ret = new LinkedHashMap(map.size()) | ||
for( Map.Entry entry : map.entrySet() ) { | ||
ret.put(entry.key, normaliseObject0(entry.value)) | ||
} | ||
return ret | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a case where you would have a closure in a list? I can't think of any
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Likely we don't any in the config, but as general solution makes sense to have it
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
This PR fixed the rendering of closures in config file reporting as strings.
For example
or