![]() R provides a standard way of documenting the objects in a package: you write. That’s one of the jobs of vignettes, which you’ll learn about in the next chapter. ![]() Similarly, object documentation is helpful if you already know the name of the object, but it doesn’t help you find the object you need to solve a given problem. It works like a dictionary: while a dictionary is helpful if you want to know what a word means, it won’t help you find the right word for a new situation. Object documentation is a type of reference documentation. In this chapter, you’ll learn about object documentation, as accessed by ? or help(). There are multiple forms of documentation. Documentation is also useful for future-you (so you remember what your functions were supposed to do), and for developers extending your package. Without it, users won’t know how to use your package. 17.3 Checking after every commit with Travisĭocumentation is one of the most important aspects of a good package.16.16 Reviewing and accepting pull requests.16.15 Submitting a pull request to another repo.8.9.2 Documenting multiple functions in the same file.8.9.1 Inheriting parameters from other functions.8.7 Documenting classes, generics and methods.7.2 Title and description: What does your package do?.7.1 Dependencies: What does your package need?.5.3 Working directory and filepath discipline.5.2.5 RStudio Project vs. active usethis project.5.1.4 Where should you create_package()?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |