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

chore: minor typo for function's description #151

Merged
merged 1 commit into from
Oct 20, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/cli/nexus-prisma.ts
Original file line number Diff line number Diff line change
Expand Up @@ -86,9 +86,9 @@ function getPrismaClientImportIdForItsGeneratorOutputConfig(
*
* How this works:
*
* 1. Get the Prisma Client generatour output path minus the trailing node_moudles/@prisma/client (if present, it could be totally custom).
* 1. Get the Prisma Client generator output path minus the trailing node_modules/@prisma/client (if present, it could be totally custom).
*
* Note that even if the user has not explicitly configured an output path in their PSL file by the time we get the geneator config from
* Note that even if the user has not explicitly configured an output path in their PSL file by the time we get the generator config from
* Prisma generator system the output default has been supplied so we always have a value here to work with.
*
* 2. Get the Nexus Prisma package path on the user's machine by starting from this module and going four directories up. Four directories
Expand All @@ -98,7 +98,7 @@ function getPrismaClientImportIdForItsGeneratorOutputConfig(
* Nexus Prisma is placed into <project>/.yalc rather than <project>/node_modules. And therefore, the check we want to achieve here would
* fail when it shouldn't.
*
* 3. With the two paths we check what the relative path between them is. If its an empty string, it means they are the same.
* 3. With the two paths we check what the relative path between them is. If it's an empty string, it means they are the same.
*
* Note this technique is better than string comparison because it guards against meaningless path difference details like windows vs posix.
* We're not certain what path standard we'll get from Prisma for example and ideally we don't care. Path.relative function should let us not
Expand Down