Provide a special class for pipeline-defined error messages about nextflow HOT 4 OPEN

Optimum would be if Nextflow can determine where the error calls come from and figure out if it's coming from pipeline source code. Could then prefix with manifest.name if set.

Then no change to pipeline source code would be required.

from nextflow.

These are two slightly different beasts. For the logger, it could be as simple as modifying the layout of messages. Although, we would then need two different loggers, one (or more) for core nextflow and another exposed to the pipeline that can be customized without affecting the others.

I don't know for sure, but I'm guessing that errors do not use logging facilities and thus need to be customized separately. Or indeed define a simple function/class method that performs some message layouting and then exits with an error code.

from nextflow.

Yes, sorry to be clear: I'm aware that the logging and error message are generated in two separate ways.

I meant more that in this case, given I'm requesting that pipeline developers can define their own errors or warnings, these should follow a common structure for familiarity for the pipeline user.

from nextflow.

Adding my comment here:
nf-core/fetchngs#309 (comment)

One of my issues was that something ends up in the channel too if ifEmpty is used. Although this might well be solved with DSL3.

from nextflow.