docs: the unit ID scan has no count - #54
Merged
Merged
Conversation
It had one for an afternoon. The results list every unit it asked, which says more than a number, so the count went out again and the changelog kept promising it. The line at the v2.3.0 tag keeps the old wording. Moving a tag over one sentence costs more than the sentence.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The changelog promised a count on the unit ID scan. It had one for an afternoon; the results list every unit it asked, which says more than a number, so it went out again in #47 and the entry kept the sentence.
The line at the
v2.3.0tag keeps the old wording. Moving a tag over one sentence costs more than the sentence.