Skip to content

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

@bodinsamuel

Description

@bodinsamuel

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions