Document language support for taginfo #22
Conversation
This file contains 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
1ec5
added
documentation
1ec5
force-pushed
the
1ec5-taginfo-language-2
branch
from
43a2b70 to
2329b44
Compare
|
This will need a rethink as of #24. I guess we could do something like pull the full list of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Factored out the language list as a plain text file for easier diffing. Now running the rendering script also uses this file to generate a taginfo project file listing all the supported
name:*subkeys. In the future, the project file template can be extended to cover other tags defined in layers (#2). The code that generates the project file requiresjqfor convenience, but if it’s a hassle to install that tool, we can replace it with some additionalsedhackery or somesuch.