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

Feat: read schema.prisma to find provider and create component #51

Open
bodinsamuel opened this issue Sep 15, 2023 · 0 comments
Open

Feat: read schema.prisma to find provider and create component #51

bodinsamuel opened this issue Sep 15, 2023 · 0 comments

Comments

@bodinsamuel
Copy link
Collaborator

Right now if a codebase is using Prismajs it's not possible to connect a service to a specific DB since it requires no additional package.
We can read the prisma file and search the provider inside it,
no need to find a parser a simple regex should do it provider.+=.+"(.+)"

That means we need to add a dependency type of "prismajs", which is definitely overkill since there will max 5 dependencies.
We can introduce the concept of a type "other" or "unknown", but that would quickly be filled with random stuff.

The solution right now imo:

  • No dependency type.
  • Parse the file with a private list of expected values
  • Create the component if that matches with the appropriate path
  • Ignore the dependency system
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

No branches or pull requests

1 participant