Would a rose by any procedurally generated name still smell as sweet?

The goal of proceduralnames is to make it easy to quickly generate random names for easy differentiation of objects or observations.

## Installation

If the CRAN badge above is green, you can install the released version of proceduralnames from CRAN with:

install.packages("proceduralnames")

You can always install the development version of proceduralnames from GitHub via:

remotes::install.github("mikemahoney218/proceduralnames")

## Usage

At the moment, proceduralnames provides three user-facing functions: make_docker_names, make_english_names, and make_spanish_names. make_docker_names makes names in the same way Docker generates names for its containers:

library(proceduralnames)
make_docker_names(1)
#> [1] "clever_chaum"

make_english_names and make_spanish_names both generate names using a subset of the 1,000 most common words in English or Spanish, respectively:

make_english_names(1)
#> [1] "name_duck_mix"
make_spanish_names(1)
#> [1] "hacerlo_programa_instituciones"

All three functions can be used to generate multiple names by providing a different number to the n argument. make_english_names and make_spanish_names both have an argument, n_words, which can be used to alter the number of words combined for each name. All three functions also have an argument, retry (named after the argument used in generating Docker container names) which will append a random integer between 1 and 10 to the end of each name:

make_docker_names(1, retry = TRUE)
#> [1] "bold_moser5"

In addition to these functions, proceduralnames provides the data sets each function draws from (namely, docker_adjectives, docker_names, common_words, and spanish_words). These data may evolve with each release of the package, so try not to depend on the length and contents of each vector remaining constant, but the fundamental shape of each object will remain stable.