Prisma ORM: Version mismatch for data migrations link

Open Beginner friendly
#31,399 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
documentation

Research direction

Open the Node / JS Prisma ORM lesson at the supplied lesson URL and locate the last link in the second assignment of the Data migrations lesson. Update it to the specified Prisma v7 data-migration guide, then verify that the lesson links directly to the v7 documentation and remains consistent with the other links.

Written by the indexing model from the issue text.

Description

Status: Help Wanted Type: Good First Issue
Checks
  • I have confirmed that the link is still broken after 3-24 hours of my initial discovery.
  • I have confirmed in the Discord community that others are having the same issue with this link.
  • This is not a duplicate of an existing issue (please have a look through our open issues list to make sure)
  • I have thoroughly read and understand The Odin Project Contributing Guide
  • Would you like to work on this issue?
Description of the broken link

The last link in the second assignment in the Prisma lesson for Data migrations lead to the latest (v8) version of the docs. Although currently there is a link in that page to the v7 version, I believe it is better to link directly to the v7 version of the guide (https://www.prisma.io/docs/guides/v7/database/data-migration), similar to the rest of the links in the assignment to avoid confusion, as there are significant changes in the instructions.

I had also noticed a recent PR #31347 that had changed the other links to v7, but it appears it had missed this specific link.

Path

Node / JS

Lesson Url

https://www.theodinproject.com/lessons/nodejs-prisma-orm

(Optional) Discord Name

No response

(Optional) Additional Comments

I am open to others making a PR for this, but if no one steps up, I can do it myself.

Dominant language
JavaScript
Stars
13.1k
Forks
16.8k
Avg merge
1d 12h
Merged PRs (30d)
26

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TheOdinProject/curriculum

All issues in TheOdinProject/curriculum

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.