Closed geanders closed 3 years ago
Where is this issue arising again?
I think this showed up when we ran check()
, somewhere in that long message output. It may be that it was something that cropped up downstream of the other problem that you fixed (https://github.com/geanders/noaastormevents/issues/26), though, in which case we might have already fixed it. Look through the output from check
and see if you see this message anywhere in there now.
I think I've sorted this out in the latest commits. There was a place in the help documentation where we had #' #'
two times in a row in one line, and I think that might have caused it.
Let's see if we can figure this one out....