Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

main,refactor: Don't use kindDefinition type in tagEntryInfo structure #1584

Merged
merged 2 commits into from
Oct 27, 2017

Conversation

masatake
Copy link
Member

To minimize a parser accessing kindDefinition data type, this commit
changes the type kind' and extensions.scopeKind' fields to int.

With this change, a parser can inspect a tagEntryInfo made in
another parser. In other word, communication between parsers
via tagEntryInfo is much easier.

Actuall example will be shown in the communiation between
JavaScript parser and VueJavaScript parser.

Signed-off-by: Masatake YAMATO <yamato@redhat.com>
To minimize a parser accessing kindDefinition data type, this commit
changes the type `kind' and `extensions.scopeKind' fields to int.

With this change, a parser can inspect a tagEntryInfo made in
another parser. In other word, communication between parsers
via tagEntryInfo is much easier.

Actuall example will be shown in the communiation between
JavaScript parser and VueJavaScript parser.

Signed-off-by: Masatake YAMATO <yamato@redhat.com>
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.005%) to 85.964% when pulling f92e6bf on masatake:cleanup-kind-infra-stage-2 into 8465ce7 on universal-ctags:master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants