casieber / ts-graphql Goto Github PK

See isQueryString.

Right now the README mentions that the custom transformers can be used with webpack loaders, but we should add a Usage section explaining how exactly to do so.

Since the library began as just playing around with the TypeScript Compiler APIs, most of the code is centralized into a couple large files, rather than following sane code organization.

Need to introduce a real structure to it.

Turn on CI loop that (for now) runs the tests

Originally the code was just some experimentation with the TypeScript Compiler APIs and writing transformers in general before it was focused to GraphQL.

Need to delete all that old experimentation code.

End goal is for this to be an npm package, but we don't currently have any of the scripts/infra in place for publishing.

Need to create a LICENSE file.

Need to check the standard ts-loader/at-loader flow for providing options to transformers.

Add the ability for user to configure the template tag token recognized as beginning a query string.

Depends on #9

Add the ability for user to configure the execution token recognized as beginning a query execution.

Depends on #9

Might need to think about this one a little more. Maybe we should just try to pick up on anything that is typed like an execution function rather than relying on a specific token? But how do we prevent false positives? Or is that even a problem?

See isQueryExecution.