You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For cases that produce an error/warning/note, such as Formatting Software Names, it would be good if we could include the message produced so that the cookbook may be discovered if people do a web search based on the message.
This does introduce a bit of a maintenance issue, as the message may change over time, but I think it will increase the usefulness of the cookbook.
The text was updated successfully, but these errors were encountered:
I started adding the standard response from CRAN team members for the last recipes (e.g.: the .GlobalEnv issue). When we are done with (most) recipes, I will go through and add them for the earlier recipes as well.
Errors/warnings/notes from the automated checks are not implemented yet. The problem there is that I don't really see them when doing CRAN work as the packages are rejected before they reach me. I suppose those issues are more likely detected by package authors of the community. @jasdumas and I are discussing good ways, how they can contribute. We will also talk a bit about this in our time meeting next week.
For cases that produce an error/warning/note, such as Formatting Software Names, it would be good if we could include the message produced so that the cookbook may be discovered if people do a web search based on the message.
This does introduce a bit of a maintenance issue, as the message may change over time, but I think it will increase the usefulness of the cookbook.
The text was updated successfully, but these errors were encountered: