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

Prettier config #38

Merged
merged 9 commits into from
Jun 10, 2024
Merged

Prettier config #38

merged 9 commits into from
Jun 10, 2024

Conversation

eriktaubeneck
Copy link
Member

@eriktaubeneck eriktaubeneck commented Jun 9, 2024

I had been using this locally, but now it's part of the pre-commit hooks and CI.

Summary by CodeRabbit

  • New Features

    • Added pre-commit hooks setup instructions to the README for easier local and GitHub usage.
    • Introduced .prettierignore file to exclude specific files and directories from Prettier formatting in the server directory.
  • Chores

    • Configured Prettier in .pre-commit-config.yaml for the server directory.
    • Added prettier dependency version 3.3.1 in server/package.json.
  • Style

    • Improved formatting in server/app/alert.tsx and server/app/query/haikunator.tsx for better readability.

@eriktaubeneck eriktaubeneck requested a review from akoshelev June 9, 2024 21:12
Copy link

vercel bot commented Jun 9, 2024

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

Name Status Preview Comments Updated (UTC)
draft ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 10, 2024 5:54pm

Copy link
Contributor

coderabbitai bot commented Jun 9, 2024

Warning

Rate limit exceeded

@eriktaubeneck has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 38 minutes and 53 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 9fee64e and 46293fc.

Walkthrough

This update introduces Prettier to the project's development workflow for consistent code formatting. It includes configuration files for Prettier and pre-commit hooks, updates to the README with setup instructions, and minor formatting changes in the codebase. Additionally, a new dependency on Prettier has been added to the server's package.json.

Changes

Files/Groups Change Summary
.git-blame-ignore-revs Added to address prettier formatting errors in the codebase.
.pre-commit-config.yaml Added Prettier configuration for the server directory.
README.md Updated with information about pre-commit hooks setup for Github and local usage instructions, including macOS details.
server/.prettierignore Specifies files and directories to be ignored by Prettier.
server/.prettierrc Added an empty object {} for Prettier configuration.
server/app/alert.tsx Added a line break within a JSX element for better formatting.
server/app/query/haikunator.tsx Refactored getCurrentTimestamp and updated NewQueryId to use encodeURIComponent with improved formatting.
server/package.json Added Prettier dependency version 3.3.1.

Poem

In lines of code, so neat and bright,
Prettier brings its formatting light.
With hooks and rules, our code refined,
A smoother path we now shall find.
Encoded queries, timestamps clear,
Our project shines, we cheer, we cheer!
🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9ca2f1f and 586fc9d.

Files ignored due to path filters (1)
  • server/package-lock.json is excluded by !**/package-lock.json
Files selected for processing (8)
  • .git-blame-ignore-revs (1 hunks)
  • .pre-commit-config.yaml (1 hunks)
  • README.md (1 hunks)
  • server/.prettierignore (1 hunks)
  • server/.prettierrc (1 hunks)
  • server/app/alert.tsx (1 hunks)
  • server/app/query/haikunator.tsx (1 hunks)
  • server/package.json (1 hunks)
Files skipped from review due to trivial changes (6)
  • .git-blame-ignore-revs
  • .pre-commit-config.yaml
  • server/.prettierignore
  • server/.prettierrc
  • server/app/alert.tsx
  • server/package.json
Additional context used
LanguageTool
README.md

[uncategorized] ~6-~6: “an” (indefinite article before a vowel sound) seems less likely than “and” (in addition to, following this). (AI_HYDRA_LEO_CP_AN_AND)
Context: ...ont end and service that starts queries an displays logs from the MPC helper serve...


[grammar] ~7-~7: “Sidecar” is a singular noun. It appears that the verb form is incorrect. (PCT_SINGULAR_NOUN_PLURAL_VERB_AGREEMENT)
Context: ...ervers 2. draft-sidecar: a sidecar back end API that runs next to the IPA binary on...


[uncategorized] ~16-~16: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...ng Locally Make sure the repo is cloned and you're working in the root directory of...


[grammar] ~46-~46: Make sure that the noun ‘setup’ is correct. Did you mean the past participle “set up”? (BE_VB_OR_NN)
Context: ...ocker #### Pre-commit Hooks Github is setup to run pre-commit hooks specified in .p...


[uncategorized] ~170-~170: When ‘IPA-specific’ is used as a modifier, it is usually spelled with a hyphen. (SPECIFIC_HYPHEN)
Context: ...ivate pip install --editable . ``` ### IPA specific certs We check in self signed certs th...


[misspelling] ~172-~172: This word is normally spelled with a hyphen. (EN_COMPOUNDS_SELF_SIGNED)
Context: ...`` ### IPA specific certs We check in self signed certs that are only for local developme...


[misspelling] ~206-~206: This word is normally spelled as one. (EN_COMPOUNDS_SUB_DOMAINS)
Context: ...ike to use. You will need to create two sub-domains, sidecar.example.com and `helper.exam...


[misspelling] ~206-~206: This word is normally spelled as one. (EN_COMPOUNDS_SUB_DOMAIN)
Context: ...ample.com. (Note, you could also use a sub-domain as your base domain, e.g., test.exampl...


[misspelling] ~206-~206: This word is normally spelled as one. (EN_COMPOUNDS_SUB_DOMAINS)
Context: ...main, e.g., test.example.com with two sub-domains of that: sidecar.test.example.com and...


[misspelling] ~223-~223: Did you mean “once”? (ONE_ONCE)
Context: ...ryone's identity (e.g., 0, 1, 2, 3) One you know these: 1. Make a config direct...


[uncategorized] ~232-~232: When ‘IPA-specific’ is used as a modifier, it is usually spelled with a hyphen. (SPECIFIC_HYPHEN)
Context: ...le.com/privkey.pem key.pem5. Generate IPA specific keys: 1. Compileipawithcargo ...

Markdownlint
README.md

13-13: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


23-23: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


50-50: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


64-64: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


83-83: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


215-215: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


223-223: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


239-239: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


248-248: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


249-249: Expected: 1; Actual: 3 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


1-1: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


250-250: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


9-9: null (MD025, single-title, single-h1)
Multiple top-level headings in the same document


250-250: null (MD025, single-title, single-h1)
Multiple top-level headings in the same document


32-32: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


139-139: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


158-158: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


164-164: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


193-193: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


198-198: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


39-39: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


68-68: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


192-192: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


199-199: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


219-219: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


225-225: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


69-69: null (MD034, no-bare-urls)
Bare URL used


70-70: null (MD034, no-bare-urls)
Bare URL used


51-51: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


65-65: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


84-84: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


106-106: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


143-143: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


188-188: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


18-18: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


26-26: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


32-32: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


55-55: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


78-78: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


86-86: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


92-92: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


98-98: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


110-110: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


116-116: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


128-128: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


134-134: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


139-139: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


149-149: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


158-158: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


164-164: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


176-176: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


193-193: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


242-242: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified

Additional comments not posted (2)
server/app/query/haikunator.tsx (2)

9-16: LGTM! The refactoring improves readability and consistency in date formatting.


20-22: LGTM! Using encodeURIComponent enhances URL safety. Ensure all usages of NewQueryId are updated to handle the encoded format.

README.md Outdated
@@ -41,6 +41,10 @@ Requirements:
3. [Supabase CLI](https://supabase.com/docs/guides/cli/getting-started)
4. Docker

#### Pre-commit Hooks

Github is setup to run pre-commit hooks specified in .pre-commit-config.yaml. If you want to use it locally, in the virtual environment, run `pre-commit install`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct the grammatical error for clarity.

- Github is setup to run pre-commit hooks specified in .pre-commit-config.yaml.
+ Github is set up to run pre-commit hooks specified in .pre-commit-config.yaml.
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Github is setup to run pre-commit hooks specified in .pre-commit-config.yaml. If you want to use it locally, in the virtual environment, run `pre-commit install`.
Github is set up to run pre-commit hooks specified in .pre-commit-config.yaml. If you want to use it locally, in the virtual environment, run `pre-commit install`.
Tools
LanguageTool

[grammar] ~46-~46: Make sure that the noun ‘setup’ is correct. Did you mean the past participle “set up”? (BE_VB_OR_NN)
Context: ...ocker #### Pre-commit Hooks Github is setup to run pre-commit hooks specified in .p...

Copy link
Collaborator

@akoshelev akoshelev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 on adding a formatter. One enforceable way to write code makes collaboration easier

.git-blame-ignore-revs Show resolved Hide resolved
server/.prettierignore Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 586fc9d and daa0999.

Files selected for processing (1)
  • server/.prettierignore (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • server/.prettierignore

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between daa0999 and 9fee64e.

Files selected for processing (1)
  • README.md (1 hunks)
Additional context used
LanguageTool
README.md

[grammar] ~6-~6: The plural noun “displays” cannot be used with the article “an”. Did you mean “an display” or “displays”? (A_NNS)
Context: ...ont end and service that starts queries an displays logs from the MPC helper servers 2. dra...


[grammar] ~7-~7: “Sidecar” is a singular noun. It appears that the verb form is incorrect. (PCT_SINGULAR_NOUN_PLURAL_VERB_AGREEMENT)
Context: ...ervers 2. draft-sidecar: a sidecar back end API that runs next to the IPA binary on...


[uncategorized] ~16-~16: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...ng Locally Make sure the repo is cloned and you're working in the root directory of...


[uncategorized] ~170-~170: When ‘IPA-specific’ is used as a modifier, it is usually spelled with a hyphen. (SPECIFIC_HYPHEN)
Context: ...ivate pip install --editable . ``` ### IPA specific certs We check in self signed certs th...


[misspelling] ~172-~172: This word is normally spelled with a hyphen. (EN_COMPOUNDS_SELF_SIGNED)
Context: ...`` ### IPA specific certs We check in self signed certs that are only for local developme...


[misspelling] ~206-~206: This word is normally spelled as one. (EN_COMPOUNDS_SUB_DOMAINS)
Context: ...ike to use. You will need to create two sub-domains, sidecar.example.com and `helper.exam...


[misspelling] ~206-~206: This word is normally spelled as one. (EN_COMPOUNDS_SUB_DOMAIN)
Context: ...ample.com. (Note, you could also use a sub-domain as your base domain, e.g., test.exampl...


[misspelling] ~206-~206: This word is normally spelled as one. (EN_COMPOUNDS_SUB_DOMAINS)
Context: ...main, e.g., test.example.com with two sub-domains of that: sidecar.test.example.com and...


[misspelling] ~223-~223: Did you mean “once”? (ONE_ONCE)
Context: ...ryone's identity (e.g., 0, 1, 2, 3) One you know these: 1. Make a config direct...


[uncategorized] ~232-~232: When ‘IPA-specific’ is used as a modifier, it is usually spelled with a hyphen. (SPECIFIC_HYPHEN)
Context: ...le.com/privkey.pem key.pem5. Generate IPA specific keys: 1. Compileipawithcargo ...

Markdownlint
README.md

13-13: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


23-23: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


50-50: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


64-64: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


83-83: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


215-215: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


223-223: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


239-239: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


248-248: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


249-249: Expected: 1; Actual: 3 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


1-1: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


250-250: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


9-9: null (MD025, single-title, single-h1)
Multiple top-level headings in the same document


250-250: null (MD025, single-title, single-h1)
Multiple top-level headings in the same document


32-32: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


139-139: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


158-158: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


164-164: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


193-193: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


198-198: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


39-39: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


68-68: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


192-192: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


199-199: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


219-219: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


225-225: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


69-69: null (MD034, no-bare-urls)
Bare URL used


70-70: null (MD034, no-bare-urls)
Bare URL used


51-51: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


65-65: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


84-84: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


106-106: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


143-143: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


188-188: null (MD036, no-emphasis-as-heading)
Emphasis used instead of a heading


18-18: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


26-26: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


32-32: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


55-55: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


78-78: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


86-86: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


92-92: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


98-98: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


110-110: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


116-116: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


128-128: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


134-134: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


139-139: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


149-149: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


158-158: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


164-164: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


176-176: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


193-193: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


242-242: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified

Additional comments not posted (1)
README.md (1)

46-46: Corrected grammatical error in the setup description.

This change improves the clarity of the documentation by using the correct form "set up" instead of "setup".

@eriktaubeneck eriktaubeneck merged commit 031145d into main Jun 10, 2024
3 checks passed
@eriktaubeneck eriktaubeneck deleted the prettier-config branch June 10, 2024 18:03
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