Add parser option to getSchema

[maxh]

I finally got around to hacking on using location data in prisma-lint!

loop-payments/prisma-lint#84

Everything works great when testing in the prisma-lint repository, but I didn't get location data when running the linter on a schema in a different repository (backend) that uses prisma-lint. I think this is because prisma-ast was looking for a config file in backend.

I wasn't sure how to get the location node configuration for prisma-ast to be set by prisma-lint without requiring backend to also have to configure prisma-ast, which felt like too much to ask for users of prisma-lint.

This PR allows prisma-lint to request location information on demand from prisma-ast, regardless of the config.

I recommend reviewing with the hide whitespace option enabled:

[MrLeebo]

This approach can work, but I'd like to tweak your implementation a little bit in order to prevent the library from constructing a new parser for each execution. That can negatively impact performance for bulk operations. Instead, we can change the getSchema config options to receive the parser instance itself. Then prisma-lint or any other library can expose its own parser and pass it into getSchema.

Example:

import { PrismaParser, getSchema } from '@mrleebo/prisma-ast'
const lintParser = new PrismaParser({ nodeLocationTracking: "full" })
getSchema(source, { parser: lintParser })

I made some code suggestions with the core ideas of the change. You'll also need to add PrismaParser to the index.ts exports

export { PrismaParser } from './parser';

The other changes you made like the visitor factory make sense and we can keep that.

[maxh]

Note: the visitor now uses the parser's config instead of receiving its own.

[maxh]

Thanks for the feedback. I've iterated in that direction -- let me know what you think.

UPDATE:

I confirmed this approach works from prisma-lint side: https://github.com/loop-payments/prisma-lint/pull/239/files

[MrLeebo]

@maxh this feature should be available via prisma-ast v0.8.0