Skip to content

Commit

Permalink
Merge pull request #212 from stepchowfun/wordsmithing
Browse files Browse the repository at this point in the history
Do some wordsmithing on the README and the help text
  • Loading branch information
stepchowfun authored Feb 22, 2024
2 parents 634b996 + f691761 commit 3345127
Show file tree
Hide file tree
Showing 5 changed files with 15 additions and 10 deletions.
5 changes: 5 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,11 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.9.1] - 2024-02-21

### Fixed
- Fixed a typo in the help text.

## [1.9.0] - 2024-02-21

### Added
Expand Down
2 changes: 1 addition & 1 deletion Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "tagref"
version = "1.9.0"
version = "1.9.1"
authors = ["Stephan Boyer <stephan@stephanboyer.com>"]
edition = "2021"
description = "Tagref helps you maintain cross-references in your code."
Expand Down
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,18 +28,18 @@ To help you manage these tags and references, Tagref checks the following:
1. References actually point to tags. A tag cannot be deleted or renamed without updating the references that point to it.
2. Tags are unique. There is never any ambiguity about which tag is being referenced.

In the example above, Tagref won't ensure that `cities` is actually non-empty. It isn't magic! It only checks the two criteria above.
In the example above, Tagref doesn't ensure that `cities` is actually non-empty. It isn't magic! It only checks the two criteria above.

In addition to references to tags, Tagref also supports *file references* and *directory references*. A file reference guarantees that the given file exists. For example:

```markdown
The program entrypoint is located in [file:src/main.rs].
```python
# If you bump the version, be sure to update [file:CHANGELOG.md].
```

A directory reference guarantees that the given directory exists. For example:

```markdown
All of the files in [dir:src] must be formatted by `rustfmt`.
```python
# This script will format the files in [dir:src].
```

## Usage
Expand Down
6 changes: 3 additions & 3 deletions src/main.rs
Original file line number Diff line number Diff line change
Expand Up @@ -70,9 +70,9 @@ fn settings() -> Settings {
"\
Tagref helps you maintain cross-references in your code.\n\
\n\
You can put tags like [tag:foo] in your code (in comments), and you can reference \
them like [ref:foo]. You can also references files like [file:src/main.rs] and \
directories like [dir:src].\n\
You can annotate your code with tags like [tag:foo] and reference them like \
[ref:foo]. You can also reference files like [file:src/main.rs] and directories like \
[dir:src].\n\
\n\
Tagref checks that tags are unique and that references are not dangling.\n\
\n\
Expand Down

0 comments on commit 3345127

Please sign in to comment.