fix: disambiguate after grouping by packages and versions #132
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.
If entries need to be disambiguated, it should be done after the entries are grouped into packages/versions to avoid having unique entries to specific version/packages not be disambiguated and left alone without a disambiguation prefix.
New example TOC:
All entries will be stripped off of the prefix unless disambiguation is required, to help shorten entries. Users will still see that they are grouped under specific packages/versions to help tell which packages/versions the entry falls under. From the above example, main difference would be that previously it would have
bigquery_storage_v1.client
andreader
, but now it simply showsclient
andreader
.Fixes #131