atwhy

What is atwhy

atwhy can be used to generate a documentation out of comments in the code.
That way you can for example describe all available options in the same file
where they are coded. A developer therefore doesn't have to know exactly where
the information has to be documented because it is just in the same file.

--> Single source of truth also for documentation!

Markdown templates are used to just group the tags together into files and add some non-code specific docu.

The idea of athwy was born during a company-hackathon and since then evolved to a first fully usable preview version.

Although most things are in a stable state, there may be small breaking changes until atwhy reaches v1.0.0.

Example

As atwhy itself uses atwhy very extensively, you can just

look at the templates folder of this project.
and search for @WHY in the whole project.

Installation

You have several options to install atwhy:

Just use docker to run a minimal image (It is multi-arch so it works on x64 and arm):
docker run --rm -i -p 4444:4444 -u $UID:$GID -v $PWD:/project ghcr.io/tiffinger-thiel-gmbh/atwhy atwhy
You may add an alias to your shell for this.
Install Go and run go install github.com/Tiffinger-Thiel-GmbH/atwhy@latest.
You may need to restart after installing Go to have the PATH setup correctly.
Download a matching binary from the releases and put somewhere in your PATH.
Note that they are currently not signed -> MacOS and Windows may not like that...

Usage

Command

Generate
If nothing special is needed, just run the command without any arguments:

atwhy

It will use the default values and just work if a templates folder with some
templates (e.g. templates/README.tpl.md) exists.
For more information run atwhy --help

Serve
You can also serve the documentation on default host localhost:4444 with:

atwhy serve

For more information run atwhy serve --help

Templates

The templates are by default inside the templates folder of your project.
Each template results in one .md file. So if you have the file templates/README.tpl.md it will be generated to README.md. If you have the file templates/doc/Usage.tpl.md it will be generated to doc/Usage.md.

The templates should be markdown files with a yaml header for metadata.

You can access a tag called @WHY example_tag using

# Example  
{{ .Tag.example_tag }}

Note: This uses the Go templating engine.
Therefore you can use the Go templating syntax.
Possible template values are:

Any Tag from the project: {{ .Tag.example_tag }}
Current date time: {{ .Now }}
Metadata from the yaml header: {{ .Meta.Title }}
Conversion of links to project-files (also in serve-mode): {{ .Project "my/file/in/the/project.go" }}
You need to use that if you want to generate links to actual files in your project.
This can also be used for pictures: ![aPicture]({{ .Project "path/to/the/picture.jpg" }})
Group of tags: {{ .Group "tag_name_prefix" }}
This concatenates all tags starting with the given tag_name_prefix and the second parameter as separator.
e.g. it matches @WHY tag_name_prefix0, @WHY tag_name_prefix1, ...
These tags get sorted alphanumeric.

What if {{ or }} is needed in the documentation?
You can wrap them with {{.Escape "..."}}.
E.g.: {{ .Escape "\"{{\" and \"}}\"" }}
Results in this markdown text: "{{" and "}}"

Note: You need to escape " with \".

(The official Go-Template way {{ "{{ -- }}" }} doesn't work in all cases with atwhy. .Escape works always.)

Header

Each template may have a yaml Header.
Example with all possible fields:

---  
# Some metadata which may be used for the generation.  
meta:  
  # The title is used for the served html to e.g. generate a menu and add page titles.  
  title: Readme # default: the template filename  
  
# Additional configuration for the `atwhy serve` command.  
server:  
  index: true # default: false  
---  
# Your Markdown starts here  
  
## Foo  
bar

(Note: VSCode supports the header automatically.)

Comments

You can specify the type of comments for each type of file. For this you may use the --comment flag.

Each --comment is a string with the following format:
--comment={extList}:{lineComment},{blockStart},{blockEnd}
Where:

extList is a comma-separated list of file extensions,
lineComment is the comment prefix for line comments, (e.g. // or #),
blockStart is the comment prefix for block comments start, (e.g. /* or <!--),
blockEnd is the comment prefix for block comments end, (e.g. */ or -->).
escape ',' by ',' if needed.
A catch-all (e.g. "://,/,/") catches all not otherwise configured extensions.
blockStart and blockEnd are optional.

Examples:

set only the lineComment for sh files
"sh:#"
set only the blockComment for html,xml
"html,xml:,"
set c-style for all files (not caught by another rule before)
"://,/*,*/"

If --comment is passed at least one time, all built-in rules are disabled.
Use --comment=DEFAULT if you still want to use the built-in rules.

The following are the default, built-in rules:

	"://,/*,*/", // All other files
	"sh:#",
	`py:#,""","""`,
	"cmd:REM",
	`cmd:::`,
	"vb:'",
	"html,xml:,<!--,-->",
	"lua:--,--[[,]]",
	"sql:--",
	"rb:#,=begin,=end",

Ignore

You can pass something like --ext ".go,.js,.ts" to only process specific files.
You can create a .atwhyignore file which just follows the .gitignore syntax.
(If you find an inconsistency with the git-handling, please report it here.)

Distribute

Prerequisites

>= Go 1.18

Build

Run go build .

This README was last updated on: 14 Feb 23 22:35 +0100

Tiffinger-Thiel-GmbH/atwhy