Change raster warning only if not explicitly supplied #7842
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Seurat Team,
This is small change to clean up console output. Currently plots based on
SingleExIPlot
orSingleDimPlot
issue a raster warning whenever the raster parameter is notFALSE
and the number of points is over 100K. However, because of this it also continuously prints the message even when user explicitly sets the parameter to be TRUE. This can clutter output especially if return lots of plots in loop for something the user has explicitly set. This was mentioned previously in #7745. While I know that you can suppress such warnings many users may not.This PR simply changes the
!isFALSE(raster)
tois.null(raster)
since NULL is the default setting. Therefore it will only print warning when setting is not explicitly provided by the user.This may have been specific design decision to warn every time plot is rasterized but seems unnecessary if user is supplying parameter. If it is specific design decision then feel free to ignore and close this PR.
Thanks as always,
Sam