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: prettier #512

Closed
wants to merge 1 commit into from
Closed

chore: prettier #512

wants to merge 1 commit into from

Conversation

plmercereau
Copy link
Contributor

@plmercereau plmercereau commented May 5, 2022

may wait until Nuno's review before merging

@vercel
Copy link

vercel bot commented May 5, 2022

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

Name Status Preview Updated
docs ✅ Ready (Inspect) Visit Preview May 5, 2022 at 3:23PM (UTC)

@changeset-bot
Copy link

changeset-bot bot commented May 5, 2022

⚠️ No Changeset found

Latest commit: 650c5eb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@szilarddoro
Copy link
Contributor

I was thinking about incorporating our Prettier configuration into DocGen. It'll always have a different output than what our formatter script would expect and therefore it'd always change the auto-generated markdown files.

I'm also struggling a lot with the import sorting. We should make our Prettier plugin's configuration (@trivago/prettier-plugin-sort-imports) consistent with our ESLint configuration.

Base automatically changed from monorepo-improvements to main May 9, 2022 07:48
@szilarddoro
Copy link
Contributor

szilarddoro commented May 19, 2022

I think we should revisit this issue at some point during a cooldown week as this PR has too many conflicts with the main branch. @plmercereau do you mind if we close this PR?

@plmercereau
Copy link
Contributor Author

Yeah, better to close it and to start again from the main branch

@szilarddoro szilarddoro deleted the refactor/prettier-monorepo branch March 10, 2023 10:23
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

Successfully merging this pull request may close these issues.

2 participants