Flesh out development section of README.

pull/9/head
Joshua Potter 2023-11-26 06:39:41 -07:00
parent 80b1f4ed49
commit 36f5bf1dfc
2 changed files with 23 additions and 10 deletions

View File

@ -8,6 +8,9 @@ build: include/*.h src/*.c
bear: include/*.h src/*.c bear: include/*.h src/*.c
@bear -- ${BUILD} @bear -- ${BUILD}
docs:
doxygen
test: test/test test: test/test
$^ $^

View File

@ -113,10 +113,11 @@ field and writes the prompt `"Prompt for field> "` to `stdout`. Since
`"fieldname"` has type `"text"`, `bootstrap` will wait for the user to input `"fieldname"` has type `"text"`, `bootstrap` will wait for the user to input
a string (submitted with a newline). a string (submitted with a newline).
If the user were to enter, say `fieldvalue`, in response to the prompt, If the user were to enter `fieldvalue` in response to the prompt, the `runner`
the `runner` script would then have access to an environment variable script would then have access to an environment variable `FIELDNAME` set to
`FIELDNAME` set to `fieldvalue` on launch. Field names should consist of `fieldvalue`. Field names should respect the [POSIX standard](https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html)
alphanumeric characters or underscores, and may not start with a digit. on environment variable naming. In particular, all field names consist solely
of alphanumeric characters or underscores and cannot start with a digit.
#### Types #### Types
@ -169,20 +170,29 @@ this.
## Development ## Development
TODO Keep in mind this tool was originally written for personal usage and as such,
any functionality (or lack thereof) reflects my own needs as I have come across
them.
### Documentation ### Documentation
TODO We use [doxygen](https://www.doxygen.nl/index.html) for documentation
generation. Run either of the following two commands to generate documentation
locally:
```bash
$> make docs
$> doxygen
```
### Formatting ### Formatting
A `pre-commit` file is included in `.githooks` to ensure consistent formatting. We use `clang-format` to ensure consistent formatting. A `pre-commit` file is
Run the following to configure `git` to use it: included in `.githooks` to enforce usage. Run the following to configure `git`
to use it:
```bash ```bash
git config --local core.hooksPath .githooks/ git config --local core.hooksPath .githooks/
``` ```
If running [direnv](https://direnv.net/), this is done automatically if `git` is If running [direnv](https://direnv.net/), this is done automatically upon
installed. entering the project directory.