Comment parsing fails if other @ comments are included

[Tam]

I'm using Postgraphile to generate a GraphQL schema from a Postgres database. Postgraphile has the concept of Smart Tags that, similar to the @type comment, use the @ symbol to be recognised.

If I have a comment like this, everything works fine:

comment on column public.attachment.file is E'@type(FileMetadata, ''../../services/Types.d'', true, false, true)';

file: FileMetadata;

But if I start including Postgraphile Smart Tags, it breaks:

comment on column public.attachment.file is E'
@behaviour -*
@type(FileMetadata, ''../../services/Types.d'', true, false, true)
';

/** \n@behaviour -*\n@type(FileMetadata, '../../services/Types.d', true, false, true)\n */
file: unknown;

Incidentally, Postgraphile also has a @type comment. So far I haven't run into conflicts with it, but that's probably because I haven't used either very much!

[kristiandupont]

Right, that would be a problem! I guess I should make those tags optional as I don't think many people use them and it's probably better solved with a hook instead. I will ponder this.