Package: fusen 0.7.2

Rename a flat file | Fully deprecate a flat file after inflate

Move from a package developed with fusen to a "classical" package

Can I be lazy in names used? | Can I knit the content of the flat template ? | How to declare packages with library() for the future vignette ? | How to include examples that cannot be run ? | Document your internal datasets in a function chunk as usual | How to ignore some chunks ? | How to create a vignette with different title and Index Entry? | How not to create a vignette? | How to get a pre-filled template for a specific function name ? | How to pre-fill multiple functions in one template | How to inflate multiple flat files ? | How to store multiple functions in a unique R file ? | All functions under one title section | Use same @rdname in function roxygen | Use same @filename in function roxygen | Use chunk param filename = "the_comon_filename" | How to read dataset that I usually put in "tests/testthat/" for my unit tests? | Can I load all functions of the current flat file during development without having to inflate()? | Can I inflate a Quarto qmd file? | Can I use {fusen} with {golem}? | How can I know if R files were created from a flat or not ? | How can I get rid of everything related to 'fusen' in my package ?

Get a tree of the package structure to help developers | Get the list of functions from a R file

{fusen} registers all files of your package | What is the configuration file? | What about unregistered files? | Deprecate flat files after inflate | Detect all files that are not registered in configuration file | How register_all_to_config() works

Inflate all your flat files at once | Store configuration of each flat file once | Prevent some flat files to be inflated | Wrapper around inflate_all() | Register all other files to help clean your project | Compute the code coverage | Complete the process with your own code style

Daily use of | Add a new set of chunks in the current Rmd | Create a new flat Rmd template | How to maintain a {fusen}? Can I use {fusen} with old-way packages ? | Option 1: Continue with the "flat_template.Rmd" | Option 2: Maintain like a classical package | What about packages already built the old way ? | Let's try to convince package developers with an example | Compare a classical way of building packages with the {fusen} way

Initiate your package and share it on GitHub | What happens behind the scene ?

All steps to create a package with {fusen} from one Rmd file | Fill your package Description | Inflate your package from the flat Rmd template | Create a new package from command line directly, using a pre-defined template | Add a new "flat_template.Rmd" template in "dev/" directory | There can be development actions | Limitations