Skip to content

Commit 7ddc74c

Browse files
authored
Merge pull request #105 from wd60622/kebab-case-typo
switch kebab typo to snake case
2 parents 6be2508 + e915eed commit 7ddc74c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/available-variables.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ This plugin offers the following variables:
44

55
| timestamp | description |
66
|:-----------|:------------|
7-
| `git-revision-date-localized` | Last git commit that touched a file. Enabled by default. |
8-
| `git-creation-date-localized` | First git commit that touched a file. Enable in [options](options.md). |
7+
| `git_revision_date_localized` | Last git commit that touched a file. Enabled by default. |
8+
| `git_creation_date_localized` | First git commit that touched a file. Enable in [options](options.md). |
99
| `git_site_revision_date_localized` | Last git commit that touched any file in the `docs/` folder. Enabled by default. |
1010

1111
You can use these variables wrapped in curly brackets (`{{` and `}}`) anywhere in a markdown file, like so:
@@ -21,8 +21,8 @@ Changing the `type`, `timezone` and/or `locale` in the [options](options.md) wil
2121

2222
If you do not want to include revision dates manually in each markdown file, or if you would like more control on the formatting, you can [override a theme](howto/override-a-theme.md). You can use the same three variables but with a `page.meta.` prefix:
2323

24-
- `page.meta.git-revision-date-localized`
25-
- `page.meta.git-creation-date-localized`
24+
- `page.meta.git_revision_date_localized`
25+
- `page.meta.git_creation_date_localized`
2626
- `page.meta.git_revision_date_localized_raw_date`
2727

2828
To allow for more flexibility when overriding a theme there are also variables for each different `type` available (regardless of the setting for `type` in [options](options.md)), where the output is also not wrapped in `<span>` elements (so you can do the CSS styling yourself):

0 commit comments

Comments
 (0)