feat: add prettier functionality for prisma and eslint

[squink13]

Closes #

✅ Checklist

• I have followed every step in the contributing guide (updated 2022-10-06).
• The PR title follows the convention we established conventional-commit
• I performed a functional test on my final commit

---

Changelog

[Short description of what has changed]

• Updated prisma and @prisma/client to 4.12.0
• Added prettier-plugin-prisma package to allow formatting of prisma schema files
• Added eslint-config-prettier to handle conflicts with eslint and prettier whenever prettier is installed as per Next.js and Prettier recommendations

---

Screenshots

[Screenshots]

create-t3-app with all options selected.

You can find the directory here

💯

[changeset-bot]

🦋 Changeset detected

Latest commit: 5bb7b9d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
create-t3-app	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
create-t3-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 4, 2023 9:21am

[github-actions]

Running Lighthouse audit...

[juliusmarminge]

I like the idea here and we should also do #1332.

I think @nexxeln objects though

[juliusmarminge]

why would we need a prettier plugin here? the prisma cli has a format command and their VSCode extension is probably a better recommendation than a 3rd party prettier plugin?

[juliusmarminge]

i wonder if it'd be a good shout to combine this installer with eslint?

so the default would be no eslint n'or prettier, and you could choose an eslint+prettier installer?

[squink13]

If you're looking at #1332 as well i think moving eslint & prettier to its own option would be nice. Not everyone wants opinionated formatting or linting for every project. It would also mimick the 'create-next-app' eslint option

[c-ehrlich]

I'm mixed about this. The more linting we add, the weirder it gets that we don't ship a "complete"/"opinionated" config. But I do lean in favour of these specific ones making sense.

Where do we want to stand on this stuff going forward? Where is the line of being too opinionated? Do we run a risk of people not realising that they're meant to add their own prettier and eslint settings? Should we pivot towards providing a reasonable "full loadout", and people can rip it out if they want?

[squink13]

I think for a better out of the box experience adding the eslint config package at the very least would be a small improvement. It gets around potential conflicts with linting and formatting.

The prisma plugin is probably more on the bloat side, its not really necessary like @juliusmarminge mentioned.

[bai]

If prisma plugin allows us to catch prisma formatting errors on CI I don't mind having it included.

My 2c is that ct3a should ship whatever the maintainers think is the best opinionated stack. Data point of one, but as an End User of ct3a I don't want to bother with linters/formatters/etc - I want to work on my app asap and I will certainly not be bothering with adding/removing linters.

[keeandev]

I believe this is a better solution if you want to abide by Prisma's official formatter with the added benefits of auto-completed relationships.

"editor.defaultFormatter": "esbenp.prettier-vscode",
"[prisma]": {
    "editor.defaultFormatter": "Prisma.prisma"
},

[juliusmarminge]

superseded by #1392