Can't get yaml parsing working

[haizaar]

I've built ctags from master (rev cbbf4fe). And I can't get the yaml pasring working:

$ ./ctags --list-languages |grep -i yaml
Yaml
$ cat /tmp/my.yml
a:
  b:
    c: 1
$ ./ctags /tmp/my.yml
$ cat tags 
!_TAG_FILE_FORMAT	2	/extended format; --format=1 will not append ;" to lines/
!_TAG_FILE_SORTED	1	/0=unsorted, 1=sorted, 2=foldcase/
!_TAG_OUTPUT_MODE	u-ctags	/u-ctags or e-ctags/
!_TAG_PROGRAM_AUTHOR	Universal Ctags Team	//
!_TAG_PROGRAM_NAME	Universal Ctags	/Derived from Exuberant Ctags/
!_TAG_PROGRAM_URL	https://ctags.io/	/official site/
!_TAG_PROGRAM_VERSION	0.0.0	/cbbf4fe/

Am I missing something?

[masatake]

Currently the yaml parser tags only anchors and aliases(only when r(reference extra tag) is enabled).

For

a:
  b:
    c: 1
    d: something

What kind of output do you expect?
a, b, c, and d? How about something?

[haizaar]

Thank you for clarifying. Since I'm new to ctags, I'll try to annotate my files with anchors and see how it goes. I need it for vim to help me working with large swagger schema​ definition yaml files. For this use case, generating tags for first two levels of keys is perfect. However since swagger format is quite specific, it may be worth creating a dedicated parser (plugin) for swagger. P.S. running `ctags --list-kinds` reveals that anchors misspelled as "anchros".

…

On 21 Mar 2017 00:10, "Masatake YAMATO" ***@***.***> wrote: Currently yaml parser tags only anchors and alias(only when r(reference extra tag) is enabled). For a: b: c: 1 d: something What kind of output do you expect? a, b, c, and d? How about something? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1322 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADjWR3Bja4rrLk5rdwJBPHteZIfXrV7ks5rnvlOgaJpZM4Mi7u2> .

[haizaar]

Tried with anchors - works fine. Thanks!

[masatake]

However since swagger format is quite specific, it may be worth creating a dedicated parser (plugin) for swagger.

That is the point.
I'm working on implementing an infrastructure (API) for writing subparsers on a base parser.
In your case yaml is a base parser and swagger is a subparser.

P.S. running ctags --list-kinds reveals that anchors misspelled as "anchros".

Thanks. Fixed in HEAD.

[haizaar]

Great. I'll appreciate if you update this post when the API is ready, so I can try it out.

[masatake]

I submit a patch set for implementing a subparser. 9ac9b7a

Swagger parser can be implemented on yaml parser with this new infrastructure. However, it is not enough.
Token API is not powerful enough. After implementing the token API, I can work on swagger parser. It takes more time.

[t-b]

I found this issue as ctags could not find anything in my gitlab-ci.yml files.
As I'm only interested in the array names starting at the start of line I added

--kinddef-Yaml=a,array,array at start of line
--regex-Yaml=/^([[:graph:]]+):[[:space:]]*^/\1/a/i

to my ctags config file. Works so far :)

[masatake]

See #3245 and #3254. Now OpenAPI/Swagger parser is available.