Skip to content

How are we checking that the code works? #20

@rpruim

Description

@rpruim

I think this is dangerous:

opts_chunk$set(eval=FALSE)

I suggest we turn that into

opts_chunk$set(include = FALSE)

That way we are less likely to have code with errors sneak through. Since a lot of the code in these labs is shown without the results, it is especially important to check that the code is indeed correct.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions