Add entity.name.type.zig
to container_decl
.
#65
Closed
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.
This way, unions, structs, enums, and error declarations get properly marked as types so that "go to definition" works properly in sublime text.
I tried to follow the "Local Development" section in README.md, but just editing the
Zig.YAML-tmLanguage
file and using PackageDev to convert it didn't update thesublime-syntax
file, which is apparently what sublime text prefers if it finds one, ignoring thetmLanguage
version. So I edited thesublime-syntax
version manually until things worked as expected, and transferred my changes to theYAML-tmLanguage
file. Then I invoked the PackageDevConvert To ()...
command but that only produced atmLanguage
file. ThetmLanguage.json
did not get updated. At that point, I was too confused by all this, being quite new to all this, so I figured I'd just get a PR going and ask for guidance.Fixes #64